FAQ
Just to show that I'm not being a complete whiner about this:

I tried a new svn update.
I tried "mvn -u"
I tried "mvn -cpu"
I tried "mvn -fae"

I tried a google search for the missing dependency.

I'm guessing the dependency I'm missing only affects the web site, but
I can't figure out how to bypass it.

On 2/25/07, Mike Kienenberger wrote:
Something broke. :-) This is a code checkout from last night (EST).

Downloading: http://repo1.maven.org/maven2/axis/axis/1.4/axis-1.4.jar
1562K downloaded
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.

Missing:
----------
1) com.atlassian.confluence:confluence-soap:jar:2.0

Try downloading the file manually from the project website.

Then, install it using the command:
mvn install:install-file -DgroupId=com.atlassian.confluence -DartifactId=c
onfluence-soap \
-Dversion=2.0 -Dpackaging=jar -Dfile=/path/to/file

Path to dependency:
1) org.apache.cayenne.build-tools:maven-cayenne-build-plugin:maven-plugi
n:3.0-SNAPSHOT
2) com.atlassian.confluence:confluence-soap:jar:2.0

----------
1 required artifact is missing.

for artifact:
org.apache.cayenne.build-tools:maven-cayenne-build-plugin:maven-plugin:3.0-SNA
PSHOT

from the specified remote repositories:
central (http://repo1.maven.org/maven2),
apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository/)


[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1 minute 5 seconds
[INFO] Finished at: Sun Feb 25 13:58:47 EST 2007
[INFO] Final Memory: 8M/16M
[INFO] ------------------------------------------------------------------------

On 2/25/07, Andrus Adamchik wrote:
As a maven-based project developer, I hate it :-)
+1 - I am with you on that.
Everything takes much longer to build.
Didn't notice that in Cayenne, but I won't be surprised - with Ant
you can tailor the build much easier.
Nothing "just works" in Eclipse anymore.
Eclipse works fine for Cayenne core modules. Itests often break,
cause they are built against unstable versions of Geronimo, OpenEjb
and pieces of third party J2EE stack components. Good thing is that
you can work with individual modules as separate projects if you have
your local repo bootstrapped from command line first.
And when something breaks or needs changing, it's beyond my skill-
set to
try to fix it.
+1 - maven breaks A LOT and it is the most convoluted build
environment that I know of.
Mind you, I haven't tried 3.0 recently because I fear maven, so in
the specific case of Cayenne, I may be overreacting.
You should - I put lots of work in making it bearable (such as
setting Eclipse project files in SVN, etc). It works now.
I know some people may want to do me physical damage for this, but
should we reconsider the maven choice?
-1

I take full responsibility for endorsing the move a year ago when the
idea was proposed - it was a mistake, and we paid for it. But
currently we have an environment that works. We are still prone to
maven "upgrades", but going back would be a bad idea as well. Here is
the benefits of Maven that we now enjoy between the sleepless nights
fixing the POMs:

* We joined the club of gullible people who bought into the Maven
hype (I thought such thing would never happen to me :-)), so now we
have a common (though crappy) platform for integration of the code
from different projects up and down stream. I remember how much pain
it was to create Maven artifacts out of Ant Cayenne in the past.

* Maven popularity leaves some (if not much) hope that it will be
fixed someday. (OT: believe it or not, even WebObjects developers are
considering Maven these days!!!)

* The project structure indeed became more organized than it was before.

* As the number of modules grows, the ability to build them one-by-
one becomes more important. You can do it with Maven, we couldn't do
it with the old Ant based system.

Andrus



Search Discussions

  • Andrus Adamchik at Feb 26, 2007 at 9:47 am
    That's coming from the ObjectStyle repo (a reference to which I nuked
    a few days ago, as it was slowing the build). Let me readd it to the
    docs module.

    Andrus

    On Feb 25, 2007, at 9:49 PM, Mike Kienenberger wrote:

    Just to show that I'm not being a complete whiner about this:

    I tried a new svn update.
    I tried "mvn -u"
    I tried "mvn -cpu"
    I tried "mvn -fae"

    I tried a google search for the missing dependency.

    I'm guessing the dependency I'm missing only affects the web site, but
    I can't figure out how to bypass it.

    On 2/25/07, Mike Kienenberger wrote:
    Something broke. :-) This is a code checkout from last night (EST).

    Downloading: http://repo1.maven.org/maven2/axis/axis/1.4/axis-1.4.jar
    1562K downloaded
    [INFO]
    ---------------------------------------------------------------------
    ---
    [ERROR] BUILD ERROR
    [INFO]
    ---------------------------------------------------------------------
    ---
    [INFO] Failed to resolve artifact.

    Missing:
    ----------
    1) com.atlassian.confluence:confluence-soap:jar:2.0

    Try downloading the file manually from the project website.

    Then, install it using the command:
    mvn install:install-file -DgroupId=com.atlassian.confluence -
    DartifactId=c
    onfluence-soap \
    -Dversion=2.0 -Dpackaging=jar -Dfile=/path/to/file

    Path to dependency:
    1) org.apache.cayenne.build-tools:maven-cayenne-build-
    plugin:maven-plugi
    n:3.0-SNAPSHOT
    2) com.atlassian.confluence:confluence-soap:jar:2.0

    ----------
    1 required artifact is missing.

    for artifact:
    org.apache.cayenne.build-tools:maven-cayenne-build-plugin:maven-
    plugin:3.0-SNA
    PSHOT

    from the specified remote repositories:
    central (http://repo1.maven.org/maven2),
    apache-snapshots (http://people.apache.org/repo/m2-snapshot-
    repository/)


    [INFO]
    ---------------------------------------------------------------------
    ---
    [INFO] For more information, run Maven with the -e switch
    [INFO]
    ---------------------------------------------------------------------
    ---
    [INFO] Total time: 1 minute 5 seconds
    [INFO] Finished at: Sun Feb 25 13:58:47 EST 2007
    [INFO] Final Memory: 8M/16M
    [INFO]
    ---------------------------------------------------------------------
    ---

    On 2/25/07, Andrus Adamchik wrote:
    As a maven-based project developer, I hate it :-)
    +1 - I am with you on that.
    Everything takes much longer to build.
    Didn't notice that in Cayenne, but I won't be surprised - with Ant
    you can tailor the build much easier.
    Nothing "just works" in Eclipse anymore.
    Eclipse works fine for Cayenne core modules. Itests often break,
    cause they are built against unstable versions of Geronimo, OpenEjb
    and pieces of third party J2EE stack components. Good thing is that
    you can work with individual modules as separate projects if you have
    your local repo bootstrapped from command line first.
    And when something breaks or needs changing, it's beyond my
    skill-
    set to
    try to fix it.
    +1 - maven breaks A LOT and it is the most convoluted build
    environment that I know of.
    Mind you, I haven't tried 3.0 recently because I fear maven,
    so in
    the specific case of Cayenne, I may be overreacting.
    You should - I put lots of work in making it bearable (such as
    setting Eclipse project files in SVN, etc). It works now.
    I know some people may want to do me physical damage for this,
    but
    should we reconsider the maven choice?
    -1

    I take full responsibility for endorsing the move a year ago when the
    idea was proposed - it was a mistake, and we paid for it. But
    currently we have an environment that works. We are still prone to
    maven "upgrades", but going back would be a bad idea as well. Here is
    the benefits of Maven that we now enjoy between the sleepless nights
    fixing the POMs:

    * We joined the club of gullible people who bought into the Maven
    hype (I thought such thing would never happen to me :-)), so now we
    have a common (though crappy) platform for integration of the code
    from different projects up and down stream. I remember how much pain
    it was to create Maven artifacts out of Ant Cayenne in the past.

    * Maven popularity leaves some (if not much) hope that it will be
    fixed someday. (OT: believe it or not, even WebObjects
    developers are
    considering Maven these days!!!)

    * The project structure indeed became more organized than it was before.
    * As the number of modules grows, the ability to build them one-by-
    one becomes more important. You can do it with Maven, we
    couldn't do
    it with the old Ant based system.

    Andrus



  • Andrus Adamchik at Feb 26, 2007 at 10:41 am
    Done, please try again.

    Andrus

    On Feb 26, 2007, at 11:46 AM, Andrus Adamchik wrote:

    That's coming from the ObjectStyle repo (a reference to which I
    nuked a few days ago, as it was slowing the build). Let me readd it
    to the docs module.

    Andrus

    On Feb 25, 2007, at 9:49 PM, Mike Kienenberger wrote:

    Just to show that I'm not being a complete whiner about this:

    I tried a new svn update.
    I tried "mvn -u"
    I tried "mvn -cpu"
    I tried "mvn -fae"

    I tried a google search for the missing dependency.

    I'm guessing the dependency I'm missing only affects the web site,
    but
    I can't figure out how to bypass it.

    On 2/25/07, Mike Kienenberger wrote:
    Something broke. :-) This is a code checkout from last night
    (EST).

    Downloading: http://repo1.maven.org/maven2/axis/axis/1.4/
    axis-1.4.jar
    1562K downloaded
    [INFO]
    --------------------------------------------------------------------
    ----
    [ERROR] BUILD ERROR
    [INFO]
    --------------------------------------------------------------------
    ----
    [INFO] Failed to resolve artifact.

    Missing:
    ----------
    1) com.atlassian.confluence:confluence-soap:jar:2.0

    Try downloading the file manually from the project website.

    Then, install it using the command:
    mvn install:install-file -DgroupId=com.atlassian.confluence
    -DartifactId=c
    onfluence-soap \
    -Dversion=2.0 -Dpackaging=jar -Dfile=/path/to/file

    Path to dependency:
    1) org.apache.cayenne.build-tools:maven-cayenne-build-
    plugin:maven-plugi
    n:3.0-SNAPSHOT
    2) com.atlassian.confluence:confluence-soap:jar:2.0

    ----------
    1 required artifact is missing.

    for artifact:
    org.apache.cayenne.build-tools:maven-cayenne-build-plugin:maven-
    plugin:3.0-SNA
    PSHOT

    from the specified remote repositories:
    central (http://repo1.maven.org/maven2),
    apache-snapshots (http://people.apache.org/repo/m2-snapshot-
    repository/)


    [INFO]
    --------------------------------------------------------------------
    ----
    [INFO] For more information, run Maven with the -e switch
    [INFO]
    --------------------------------------------------------------------
    ----
    [INFO] Total time: 1 minute 5 seconds
    [INFO] Finished at: Sun Feb 25 13:58:47 EST 2007
    [INFO] Final Memory: 8M/16M
    [INFO]
    --------------------------------------------------------------------
    ----

    On 2/25/07, Andrus Adamchik wrote:
    As a maven-based project developer, I hate it :-)
    +1 - I am with you on that.
    Everything takes much longer to build.
    Didn't notice that in Cayenne, but I won't be surprised - with Ant
    you can tailor the build much easier.
    Nothing "just works" in Eclipse anymore.
    Eclipse works fine for Cayenne core modules. Itests often break,
    cause they are built against unstable versions of Geronimo, OpenEjb
    and pieces of third party J2EE stack components. Good thing is that
    you can work with individual modules as separate projects if you have
    your local repo bootstrapped from command line first.
    And when something breaks or needs changing, it's beyond my
    skill-
    set to
    try to fix it.
    +1 - maven breaks A LOT and it is the most convoluted build
    environment that I know of.
    Mind you, I haven't tried 3.0 recently because I fear maven,
    so in
    the specific case of Cayenne, I may be overreacting.
    You should - I put lots of work in making it bearable (such as
    setting Eclipse project files in SVN, etc). It works now.
    I know some people may want to do me physical damage for
    this, but
    should we reconsider the maven choice?
    -1

    I take full responsibility for endorsing the move a year ago when the
    idea was proposed - it was a mistake, and we paid for it. But
    currently we have an environment that works. We are still prone to
    maven "upgrades", but going back would be a bad idea as well. Here is
    the benefits of Maven that we now enjoy between the sleepless nights
    fixing the POMs:

    * We joined the club of gullible people who bought into the Maven
    hype (I thought such thing would never happen to me :-)), so now we
    have a common (though crappy) platform for integration of the code
    from different projects up and down stream. I remember how much pain
    it was to create Maven artifacts out of Ant Cayenne in the past.

    * Maven popularity leaves some (if not much) hope that it will be
    fixed someday. (OT: believe it or not, even WebObjects
    developers are
    considering Maven these days!!!)

    * The project structure indeed became more organized than it
    was before.
    * As the number of modules grows, the ability to build them one- by-
    one becomes more important. You can do it with Maven, we
    couldn't do
    it with the old Ant based system.

    Andrus



  • Mike Kienenberger at Feb 26, 2007 at 4:19 pm

    On 2/26/07, Andrus Adamchik wrote:
    Done, please try again.
    Ok. I have new probably-unrelated errors (next message). However,
    it seems odd to me that the dependencies for building the web site
    would block the rest of the cayenne build. Is this something we can
    fix down the road?
  • Mike Kienenberger at Feb 26, 2007 at 4:21 pm

    On 2/26/07, Andrus Adamchik wrote:
    Done, please try again.
    Next problem set. 4 more missing jars. With enough time, I could
    probably locate and manually install these, but I'm guessing that
    shouldn't be necessary

    [ERROR] BUILD ERROR
    [INFO] ------------------------------------------------------------------------
    [INFO] Failed to resolve artifact.

    Missing:
    ----------
    1) opensymphony:oscache:jar:2.3.2

    Try downloading the file manually from the project website.

    Then, install it using the command:
    mvn install:install-file -DgroupId=opensymphony -DartifactId=oscache \
    -Dversion=2.3.2 -Dpackaging=jar -Dfile=/path/to/file

    Path to dependency:
    1) org.apache.cayenne.unpublished:cayenne-jdk1.4-unpublished:jar:3.0-SNA
    PSHOT
    2) opensymphony:oscache:jar:2.3.2

    2) foundrylogic.vpp:vpp:jar:2.2.1

    Try downloading the file manually from the project website.

    Then, install it using the command:
    mvn install:install-file -DgroupId=foundrylogic.vpp -DartifactId=vpp \
    -Dversion=2.2.1 -Dpackaging=jar -Dfile=/path/to/file

    Path to dependency:
    1) org.apache.cayenne.unpublished:cayenne-jdk1.4-unpublished:jar:3.0-SNA
    PSHOT
    2) foundrylogic.vpp:vpp:jar:2.2.1

    3) mockrunner:mockrunner:jar:0.3.7

    Try downloading the file manually from the project website.

    Then, install it using the command:
    mvn install:install-file -DgroupId=mockrunner -DartifactId=mockrunner \
    -Dversion=0.3.7 -Dpackaging=jar -Dfile=/path/to/file

    Path to dependency:
    1) org.apache.cayenne.unpublished:cayenne-jdk1.4-unpublished:jar:3.0-SNA
    PSHOT
    2) mockrunner:mockrunner:jar:0.3.7

    4) com.caucho:hessian:jar:3.0.20

    Try downloading the file manually from the project website.

    Then, install it using the command:
    mvn install:install-file -DgroupId=com.caucho -DartifactId=hessian \
    -Dversion=3.0.20 -Dpackaging=jar -Dfile=/path/to/file

    Path to dependency:
    1) org.apache.cayenne.unpublished:cayenne-jdk1.4-unpublished:jar:3.0-SNA
    PSHOT
    2) com.caucho:hessian:jar:3.0.20

    ----------
    4 required artifacts are missing.

    for artifact:
    org.apache.cayenne.unpublished:cayenne-jdk1.4-unpublished:jar:3.0-SNAPSHOT

    from the specified remote repositories:
    central (http://repo1.maven.org/maven2),
    apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository/)


    [INFO] ------------------------------------------------------------------------
    [INFO] For more information, run Maven with the -e switch
    [INFO] ------------------------------------------------------------------------
    [INFO] Total time: 15 seconds
    [INFO] Finished at: Mon Feb 26 11:19:23 EST 2007
    [INFO] Final Memory: 13M/23M
    [INFO] ------------------------------------------------------------------------
  • Andrus Adamchik at Feb 26, 2007 at 4:26 pm
    Doh, that's the same exact problem. I guess I need a separate fake
    dependency module that points to ObjectStyle repo for all those jars,
    preventing the rest of the build from accessing objectstyle.

    Andrus

    On Feb 26, 2007, at 6:21 PM, Mike Kienenberger wrote:
    On 2/26/07, Andrus Adamchik wrote:
    Done, please try again.
    Next problem set. 4 more missing jars. With enough time, I could
    probably locate and manually install these, but I'm guessing that
    shouldn't be necessary

    [ERROR] BUILD ERROR
    [INFO]
    ----------------------------------------------------------------------
    --
    [INFO] Failed to resolve artifact.

    Missing:
    ----------
    1) opensymphony:oscache:jar:2.3.2

    Try downloading the file manually from the project website.

    Then, install it using the command:
    mvn install:install-file -DgroupId=opensymphony -
    DartifactId=oscache \
    -Dversion=2.3.2 -Dpackaging=jar -Dfile=/path/to/file

    Path to dependency:
    1) org.apache.cayenne.unpublished:cayenne-jdk1.4-
    unpublished:jar:3.0-SNA
    PSHOT
    2) opensymphony:oscache:jar:2.3.2

    2) foundrylogic.vpp:vpp:jar:2.2.1

    Try downloading the file manually from the project website.

    Then, install it using the command:
    mvn install:install-file -DgroupId=foundrylogic.vpp -
    DartifactId=vpp \
    -Dversion=2.2.1 -Dpackaging=jar -Dfile=/path/to/file

    Path to dependency:
    1) org.apache.cayenne.unpublished:cayenne-jdk1.4-
    unpublished:jar:3.0-SNA
    PSHOT
    2) foundrylogic.vpp:vpp:jar:2.2.1

    3) mockrunner:mockrunner:jar:0.3.7

    Try downloading the file manually from the project website.

    Then, install it using the command:
    mvn install:install-file -DgroupId=mockrunner -
    DartifactId=mockrunner \
    -Dversion=0.3.7 -Dpackaging=jar -Dfile=/path/to/file

    Path to dependency:
    1) org.apache.cayenne.unpublished:cayenne-jdk1.4-
    unpublished:jar:3.0-SNA
    PSHOT
    2) mockrunner:mockrunner:jar:0.3.7

    4) com.caucho:hessian:jar:3.0.20

    Try downloading the file manually from the project website.

    Then, install it using the command:
    mvn install:install-file -DgroupId=com.caucho -
    DartifactId=hessian \
    -Dversion=3.0.20 -Dpackaging=jar -Dfile=/path/to/file

    Path to dependency:
    1) org.apache.cayenne.unpublished:cayenne-jdk1.4-
    unpublished:jar:3.0-SNA
    PSHOT
    2) com.caucho:hessian:jar:3.0.20

    ----------
    4 required artifacts are missing.

    for artifact:
    org.apache.cayenne.unpublished:cayenne-jdk1.4-unpublished:jar:3.0-
    SNAPSHOT

    from the specified remote repositories:
    central (http://repo1.maven.org/maven2),
    apache-snapshots (http://people.apache.org/repo/m2-snapshot-
    repository/)


    [INFO]
    ----------------------------------------------------------------------
    --
    [INFO] For more information, run Maven with the -e switch
    [INFO]
    ----------------------------------------------------------------------
    --
    [INFO] Total time: 15 seconds
    [INFO] Finished at: Mon Feb 26 11:19:23 EST 2007
    [INFO] Final Memory: 13M/23M
    [INFO]
    ----------------------------------------------------------------------
    --
  • Andrus Adamchik at Feb 26, 2007 at 4:31 pm
    Done - added the needed dependencies to build-tools/maven-cayenne-
    build-plugin POM, so that they are bootstrapped from ObjectStyle.

    Andrus

    On Feb 26, 2007, at 6:25 PM, Andrus Adamchik wrote:

    Doh, that's the same exact problem. I guess I need a separate fake
    dependency module that points to ObjectStyle repo for all those
    jars, preventing the rest of the build from accessing objectstyle.

    Andrus

    On Feb 26, 2007, at 6:21 PM, Mike Kienenberger wrote:
    On 2/26/07, Andrus Adamchik wrote:
    Done, please try again.
    Next problem set. 4 more missing jars. With enough time, I could
    probably locate and manually install these, but I'm guessing that
    shouldn't be necessary

    [ERROR] BUILD ERROR
    [INFO]
    ---------------------------------------------------------------------
    ---
    [INFO] Failed to resolve artifact.

    Missing:
    ----------
    1) opensymphony:oscache:jar:2.3.2

    Try downloading the file manually from the project website.

    Then, install it using the command:
    mvn install:install-file -DgroupId=opensymphony -
    DartifactId=oscache \
    -Dversion=2.3.2 -Dpackaging=jar -Dfile=/path/to/file

    Path to dependency:
    1) org.apache.cayenne.unpublished:cayenne-jdk1.4-
    unpublished:jar:3.0-SNA
    PSHOT
    2) opensymphony:oscache:jar:2.3.2

    2) foundrylogic.vpp:vpp:jar:2.2.1

    Try downloading the file manually from the project website.

    Then, install it using the command:
    mvn install:install-file -DgroupId=foundrylogic.vpp -
    DartifactId=vpp \
    -Dversion=2.2.1 -Dpackaging=jar -Dfile=/path/to/file

    Path to dependency:
    1) org.apache.cayenne.unpublished:cayenne-jdk1.4-
    unpublished:jar:3.0-SNA
    PSHOT
    2) foundrylogic.vpp:vpp:jar:2.2.1

    3) mockrunner:mockrunner:jar:0.3.7

    Try downloading the file manually from the project website.

    Then, install it using the command:
    mvn install:install-file -DgroupId=mockrunner -
    DartifactId=mockrunner \
    -Dversion=0.3.7 -Dpackaging=jar -Dfile=/path/to/file

    Path to dependency:
    1) org.apache.cayenne.unpublished:cayenne-jdk1.4-
    unpublished:jar:3.0-SNA
    PSHOT
    2) mockrunner:mockrunner:jar:0.3.7

    4) com.caucho:hessian:jar:3.0.20

    Try downloading the file manually from the project website.

    Then, install it using the command:
    mvn install:install-file -DgroupId=com.caucho -
    DartifactId=hessian \
    -Dversion=3.0.20 -Dpackaging=jar -Dfile=/path/to/file

    Path to dependency:
    1) org.apache.cayenne.unpublished:cayenne-jdk1.4-
    unpublished:jar:3.0-SNA
    PSHOT
    2) com.caucho:hessian:jar:3.0.20

    ----------
    4 required artifacts are missing.

    for artifact:
    org.apache.cayenne.unpublished:cayenne-jdk1.4-unpublished:jar:3.0-
    SNAPSHOT

    from the specified remote repositories:
    central (http://repo1.maven.org/maven2),
    apache-snapshots (http://people.apache.org/repo/m2-snapshot-
    repository/)


    [INFO]
    ---------------------------------------------------------------------
    ---
    [INFO] For more information, run Maven with the -e switch
    [INFO]
    ---------------------------------------------------------------------
    ---
    [INFO] Total time: 15 seconds
    [INFO] Finished at: Mon Feb 26 11:19:23 EST 2007
    [INFO] Final Memory: 13M/23M
    [INFO]
    ---------------------------------------------------------------------
    ---
  • Andrus Adamchik at Feb 26, 2007 at 4:24 pm
    They part of the same custom build plugin. Of course we can split it
    in multiple small plugins, but then the maintenance would become much
    harder.

    Andrus
    On Feb 26, 2007, at 6:19 PM, Mike Kienenberger wrote:
    On 2/26/07, Andrus Adamchik wrote:
    Done, please try again.
    Ok. I have new probably-unrelated errors (next message). However,
    it seems odd to me that the dependencies for building the web site
    would block the rest of the cayenne build. Is this something we can
    fix down the road?
  • Mike Kienenberger at Feb 26, 2007 at 4:56 pm
    But isn't the whole point of using maven that this various modules can
    be built independently, provided the minimal dependencies are met?

    I don't think something like the web site (which a regular cayenne
    user doesn't need) should be a dependency of the runtime/modeler.
    On 2/26/07, Andrus Adamchik wrote:
    They part of the same custom build plugin. Of course we can split it
    in multiple small plugins, but then the maintenance would become much
    harder.

    Andrus
    On Feb 26, 2007, at 6:19 PM, Mike Kienenberger wrote:
    On 2/26/07, Andrus Adamchik wrote:
    Done, please try again.
    Ok. I have new probably-unrelated errors (next message). However,
    it seems odd to me that the dependencies for building the web site
    would block the rest of the cayenne build. Is this something we can
    fix down the road?
  • Andrus Adamchik at Feb 26, 2007 at 5:00 pm
    Sure we can split the plugin, and put the docs mojo in the docs
    folder. Yet another module to maintain ;-)

    On Feb 26, 2007, at 6:55 PM, Mike Kienenberger wrote:
    But isn't the whole point of using maven that this various modules can
    be built independently, provided the minimal dependencies are met?

    I don't think something like the web site (which a regular cayenne
    user doesn't need) should be a dependency of the runtime/modeler.
    On 2/26/07, Andrus Adamchik wrote:
    They part of the same custom build plugin. Of course we can split it
    in multiple small plugins, but then the maintenance would become much
    harder.

    Andrus
    On Feb 26, 2007, at 6:19 PM, Mike Kienenberger wrote:
    On 2/26/07, Andrus Adamchik wrote:
    Done, please try again.
    Ok. I have new probably-unrelated errors (next message). However,
    it seems odd to me that the dependencies for building the web site
    would block the rest of the cayenne build. Is this something we can
    fix down the road?
  • Mike Kienenberger at Feb 26, 2007 at 5:09 pm
    :-)

    I think that makes the most sense as I suspect doc- and web-related
    dependencies are more fragile than regular code. At least, I've seen
    these things break more often in MyFaces than the standard library
    build tools.
    On 2/26/07, Andrus Adamchik wrote:
    Sure we can split the plugin, and put the docs mojo in the docs
    folder. Yet another module to maintain ;-)

    On Feb 26, 2007, at 6:55 PM, Mike Kienenberger wrote:
    But isn't the whole point of using maven that this various modules can
    be built independently, provided the minimal dependencies are met?

    I don't think something like the web site (which a regular cayenne
    user doesn't need) should be a dependency of the runtime/modeler.
    On 2/26/07, Andrus Adamchik wrote:
    They part of the same custom build plugin. Of course we can split it
    in multiple small plugins, but then the maintenance would become much
    harder.

    Andrus
    On Feb 26, 2007, at 6:19 PM, Mike Kienenberger wrote:
    On 2/26/07, Andrus Adamchik wrote:
    Done, please try again.
    Ok. I have new probably-unrelated errors (next message). However,
    it seems odd to me that the dependencies for building the web site
    would block the rest of the cayenne build. Is this something we can
    fix down the road?
  • Mike Kienenberger at Feb 26, 2007 at 5:10 pm
    Here's the next error.

    [ERROR] BUILD ERROR
    [INFO] ------------------------------------------------------------------------
    [INFO] Failed to resolve artifact.

    Missing:
    ----------
    1) jgoodies:looks:jar:1.3.1

    Try downloading the file manually from the project website.

    Then, install it using the command:
    mvn install:install-file -DgroupId=jgoodies -DartifactId=looks \
    -Dversion=1.3.1 -Dpackaging=jar -Dfile=/path/to/file

    Path to dependency:
    1) org.apache.cayenne:cayenne-modeler:jar:3.0-SNAPSHOT
    2) jgoodies:looks:jar:1.3.1

    ----------
    1 required artifact is missing.

    for artifact:
    org.apache.cayenne:cayenne-modeler:jar:3.0-SNAPSHOT

    from the specified remote repositories:
    central (http://repo1.maven.org/maven2),
    apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository/)


    [INFO] ------------------------------------------------------------------------
    [INFO] For more information, run Maven with the -e switch
    [INFO] ------------------------------------------------------------------------
    [INFO] Total time: 3 minutes 9 seconds
    [INFO] Finished at: Mon Feb 26 12:09:53 EST 2007
    [INFO] Final Memory: 16M/29M
    [INFO] ------------------------------------------------------------------------
    On 2/26/07, Mike Kienenberger wrote:
    :-)

    I think that makes the most sense as I suspect doc- and web-related
    dependencies are more fragile than regular code. At least, I've seen
    these things break more often in MyFaces than the standard library
    build tools.
    On 2/26/07, Andrus Adamchik wrote:
    Sure we can split the plugin, and put the docs mojo in the docs
    folder. Yet another module to maintain ;-)

    On Feb 26, 2007, at 6:55 PM, Mike Kienenberger wrote:
    But isn't the whole point of using maven that this various modules can
    be built independently, provided the minimal dependencies are met?

    I don't think something like the web site (which a regular cayenne
    user doesn't need) should be a dependency of the runtime/modeler.
    On 2/26/07, Andrus Adamchik wrote:
    They part of the same custom build plugin. Of course we can split it
    in multiple small plugins, but then the maintenance would become much
    harder.

    Andrus
    On Feb 26, 2007, at 6:19 PM, Mike Kienenberger wrote:
    On 2/26/07, Andrus Adamchik wrote:
    Done, please try again.
    Ok. I have new probably-unrelated errors (next message). However,
    it seems odd to me that the dependencies for building the web site
    would block the rest of the cayenne build. Is this something we can
    fix down the road?
  • Andrus Adamchik at Feb 26, 2007 at 5:41 pm
    Fixed.
    On Feb 26, 2007, at 7:09 PM, Mike Kienenberger wrote:

    Here's the next error.

    [ERROR] BUILD ERROR
    [INFO]
    ----------------------------------------------------------------------
    --
    [INFO] Failed to resolve artifact.

    Missing:
    ----------
    1) jgoodies:looks:jar:1.3.1

    Try downloading the file manually from the project website.

    Then, install it using the command:
    mvn install:install-file -DgroupId=jgoodies -DartifactId=looks \
    -Dversion=1.3.1 -Dpackaging=jar -Dfile=/path/to/file

    Path to dependency:
    1) org.apache.cayenne:cayenne-modeler:jar:3.0-SNAPSHOT
    2) jgoodies:looks:jar:1.3.1

    ----------
    1 required artifact is missing.

    for artifact:
    org.apache.cayenne:cayenne-modeler:jar:3.0-SNAPSHOT

    from the specified remote repositories:
    central (http://repo1.maven.org/maven2),
    apache-snapshots (http://people.apache.org/repo/m2-snapshot-
    repository/)


    [INFO]
    ----------------------------------------------------------------------
    --
    [INFO] For more information, run Maven with the -e switch
    [INFO]
    ----------------------------------------------------------------------
    --
    [INFO] Total time: 3 minutes 9 seconds
    [INFO] Finished at: Mon Feb 26 12:09:53 EST 2007
    [INFO] Final Memory: 16M/29M
    [INFO]
    ----------------------------------------------------------------------
    --
    On 2/26/07, Mike Kienenberger wrote:
    :-)

    I think that makes the most sense as I suspect doc- and web-related
    dependencies are more fragile than regular code. At least, I've
    seen
    these things break more often in MyFaces than the standard library
    build tools.
    On 2/26/07, Andrus Adamchik wrote:
    Sure we can split the plugin, and put the docs mojo in the docs
    folder. Yet another module to maintain ;-)

    On Feb 26, 2007, at 6:55 PM, Mike Kienenberger wrote:
    But isn't the whole point of using maven that this various
    modules can
    be built independently, provided the minimal dependencies are
    met?
    I don't think something like the web site (which a regular
    cayenne
    user doesn't need) should be a dependency of the runtime/modeler.
    On 2/26/07, Andrus Adamchik wrote:
    They part of the same custom build plugin. Of course we can
    split it
    in multiple small plugins, but then the maintenance would
    become much
    harder.

    Andrus
    On Feb 26, 2007, at 6:19 PM, Mike Kienenberger wrote:
    On 2/26/07, Andrus Adamchik wrote:
    Done, please try again.
    Ok. I have new probably-unrelated errors (next message). However,
    it seems odd to me that the dependencies for building the
    web site
    would block the rest of the cayenne build. Is this something we can
    fix down the road?
  • Mike Kienenberger at Feb 26, 2007 at 6:02 pm
    I'm now up to failing integration tests. You probably already know
    about these. I'll look up the skip tests command and let you know how
    it goes from there.


    -------------------------------------------------------
    T E S T S
    -------------------------------------------------------
    Running org.apache.cayenne.jpa.itest.ch5._5_4_EntityMnagerFactoryTest
    Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.922 sec
    Running org.apache.cayenne.jpa.itest.ch5._5_5_1_JtaEntityManagerTest
    Apache OpenEJB 3.0-incubating-SNAPSHOT build: 20070224-02:26
    http://incubator.apache.org/openejb
    Cannot find the configuration file [conf/openejb.xml]. Creating one at C:\works
    paces\cayenne\cayenne-2007-02-24-2034\itests\jpa-chapter5\target\openejb-out\con
    f\openejb.xml
    OpenEJB ready.
    Will transform: org/apache/cayenne/jpa/itest/ch5/entity/SimpleEntity
    Tests run: 2, Failures: 1, Errors: 1, Skipped: 0, Time elapsed: 2.015 sec <<< FA
    ILURE!
    Running org.apache.cayenne.jpa.itest.ch5._5_5_2_ResourceLocalEntityManagerTest
    Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.094 sec

    Results :
    Tests run: 5, Failures: 1, Errors: 1, Skipped: 0

    [INFO] ------------------------------------------------------------------------
    [ERROR] BUILD FAILURE
    [INFO] ------------------------------------------------------------------------
    [INFO] There are test failures.
    [INFO] ------------------------------------------------------------------------
    [INFO] For more information, run Maven with the -e switch
    [INFO] ------------------------------------------------------------------------
    [INFO] Total time: 6 minutes 37 seconds
    [INFO] Finished at: Mon Feb 26 12:53:40 EST 2007
    [INFO] Final Memory: 26M/47M
    [INFO] ------------------------------------------------------------------------
    On 2/26/07, Andrus Adamchik wrote:
    Fixed.
    On Feb 26, 2007, at 7:09 PM, Mike Kienenberger wrote:

    Here's the next error.

    [ERROR] BUILD ERROR
    [INFO]
    ----------------------------------------------------------------------
    --
    [INFO] Failed to resolve artifact.

    Missing:
    ----------
    1) jgoodies:looks:jar:1.3.1

    Try downloading the file manually from the project website.

    Then, install it using the command:
    mvn install:install-file -DgroupId=jgoodies -DartifactId=looks \
    -Dversion=1.3.1 -Dpackaging=jar -Dfile=/path/to/file

    Path to dependency:
    1) org.apache.cayenne:cayenne-modeler:jar:3.0-SNAPSHOT
    2) jgoodies:looks:jar:1.3.1

    ----------
    1 required artifact is missing.

    for artifact:
    org.apache.cayenne:cayenne-modeler:jar:3.0-SNAPSHOT

    from the specified remote repositories:
    central (http://repo1.maven.org/maven2),
    apache-snapshots (http://people.apache.org/repo/m2-snapshot-
    repository/)


    [INFO]
    ----------------------------------------------------------------------
    --
    [INFO] For more information, run Maven with the -e switch
    [INFO]
    ----------------------------------------------------------------------
    --
    [INFO] Total time: 3 minutes 9 seconds
    [INFO] Finished at: Mon Feb 26 12:09:53 EST 2007
    [INFO] Final Memory: 16M/29M
    [INFO]
    ----------------------------------------------------------------------
    --
    On 2/26/07, Mike Kienenberger wrote:
    :-)

    I think that makes the most sense as I suspect doc- and web-related
    dependencies are more fragile than regular code. At least, I've
    seen
    these things break more often in MyFaces than the standard library
    build tools.
    On 2/26/07, Andrus Adamchik wrote:
    Sure we can split the plugin, and put the docs mojo in the docs
    folder. Yet another module to maintain ;-)

    On Feb 26, 2007, at 6:55 PM, Mike Kienenberger wrote:
    But isn't the whole point of using maven that this various
    modules can
    be built independently, provided the minimal dependencies are
    met?
    I don't think something like the web site (which a regular
    cayenne
    user doesn't need) should be a dependency of the runtime/modeler.
    On 2/26/07, Andrus Adamchik wrote:
    They part of the same custom build plugin. Of course we can
    split it
    in multiple small plugins, but then the maintenance would
    become much
    harder.

    Andrus
    On Feb 26, 2007, at 6:19 PM, Mike Kienenberger wrote:
    On 2/26/07, Andrus Adamchik wrote:
    Done, please try again.
    Ok. I have new probably-unrelated errors (next message). However,
    it seems odd to me that the dependencies for building the
    web site
    would block the rest of the cayenne build. Is this something we can
    fix down the road?
  • Andrus Adamchik at Feb 26, 2007 at 6:08 pm
    Yep - this is due to a bug in Geronimo TX manager:

    https://issues.apache.org/jira/browse/GERONIMO-2809

    It is fixed in svn, so you can build 'geronimo-transaction' module
    locally or ignore the tests.

    Andrus


    On Feb 26, 2007, at 8:01 PM, Mike Kienenberger wrote:

    I'm now up to failing integration tests. You probably already know
    about these. I'll look up the skip tests command and let you know how
    it goes from there.


    -------------------------------------------------------
    T E S T S
    -------------------------------------------------------
    Running org.apache.cayenne.jpa.itest.ch5._5_4_EntityMnagerFactoryTest
    Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
    0.922 sec
    Running org.apache.cayenne.jpa.itest.ch5._5_5_1_JtaEntityManagerTest
    Apache OpenEJB 3.0-incubating-SNAPSHOT build: 20070224-02:26
    http://incubator.apache.org/openejb
    Cannot find the configuration file [conf/openejb.xml]. Creating
    one at C:\works
    paces\cayenne\cayenne-2007-02-24-2034\itests\jpa-chapter5\target
    \openejb-out\con
    f\openejb.xml
    OpenEJB ready.
    Will transform: org/apache/cayenne/jpa/itest/ch5/entity/SimpleEntity
    Tests run: 2, Failures: 1, Errors: 1, Skipped: 0, Time elapsed:
    2.015 sec <<< FA
    ILURE!
    Running
    org.apache.cayenne.jpa.itest.ch5._5_5_2_ResourceLocalEntityManagerTest
    Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
    0.094 sec

    Results :
    Tests run: 5, Failures: 1, Errors: 1, Skipped: 0

    [INFO]
    ----------------------------------------------------------------------
    --
    [ERROR] BUILD FAILURE
    [INFO]
    ----------------------------------------------------------------------
    --
    [INFO] There are test failures.
    [INFO]
    ----------------------------------------------------------------------
    --
    [INFO] For more information, run Maven with the -e switch
    [INFO]
    ----------------------------------------------------------------------
    --
    [INFO] Total time: 6 minutes 37 seconds
    [INFO] Finished at: Mon Feb 26 12:53:40 EST 2007
    [INFO] Final Memory: 26M/47M
    [INFO]
    ----------------------------------------------------------------------
    --
    On 2/26/07, Andrus Adamchik wrote:
    Fixed.
    On Feb 26, 2007, at 7:09 PM, Mike Kienenberger wrote:

    Here's the next error.

    [ERROR] BUILD ERROR
    [INFO]
    ---------------------------------------------------------------------
    -
    --
    [INFO] Failed to resolve artifact.

    Missing:
    ----------
    1) jgoodies:looks:jar:1.3.1

    Try downloading the file manually from the project website.

    Then, install it using the command:
    mvn install:install-file -DgroupId=jgoodies -
    DartifactId=looks \
    -Dversion=1.3.1 -Dpackaging=jar -Dfile=/path/to/file

    Path to dependency:
    1) org.apache.cayenne:cayenne-modeler:jar:3.0-SNAPSHOT
    2) jgoodies:looks:jar:1.3.1

    ----------
    1 required artifact is missing.

    for artifact:
    org.apache.cayenne:cayenne-modeler:jar:3.0-SNAPSHOT

    from the specified remote repositories:
    central (http://repo1.maven.org/maven2),
    apache-snapshots (http://people.apache.org/repo/m2-snapshot-
    repository/)


    [INFO]
    ---------------------------------------------------------------------
    -
    --
    [INFO] For more information, run Maven with the -e switch
    [INFO]
    ---------------------------------------------------------------------
    -
    --
    [INFO] Total time: 3 minutes 9 seconds
    [INFO] Finished at: Mon Feb 26 12:09:53 EST 2007
    [INFO] Final Memory: 16M/29M
    [INFO]
    ---------------------------------------------------------------------
    -
    --
    On 2/26/07, Mike Kienenberger wrote:
    :-)

    I think that makes the most sense as I suspect doc- and web-
    related
    dependencies are more fragile than regular code. At least, I've
    seen
    these things break more often in MyFaces than the standard library
    build tools.
    On 2/26/07, Andrus Adamchik wrote:
    Sure we can split the plugin, and put the docs mojo in the docs
    folder. Yet another module to maintain ;-)

    On Feb 26, 2007, at 6:55 PM, Mike Kienenberger wrote:
    But isn't the whole point of using maven that this various
    modules can
    be built independently, provided the minimal dependencies are
    met?
    I don't think something like the web site (which a regular
    cayenne
    user doesn't need) should be a dependency of the runtime/
    modeler.
    On 2/26/07, Andrus Adamchik wrote:
    They part of the same custom build plugin. Of course we can
    split it
    in multiple small plugins, but then the maintenance would
    become much
    harder.

    Andrus
    On Feb 26, 2007, at 6:19 PM, Mike Kienenberger wrote:
    On 2/26/07, Andrus Adamchik wrote:
    Done, please try again.
    Ok. I have new probably-unrelated errors (next message). However,
    it seems odd to me that the dependencies for building the
    web site
    would block the rest of the cayenne build. Is this
    something
    we can
    fix down the road?
  • Mike Kienenberger at Feb 26, 2007 at 6:23 pm
    Ok. Finally built it. Build time 16 minutes and 32 seconds, with
    skip-tests enabled. I'm going to do another build to see if this was
    still downloading dependencies in the last build.
    On 2/26/07, Andrus Adamchik wrote:
    Yep - this is due to a bug in Geronimo TX manager:

    https://issues.apache.org/jira/browse/GERONIMO-2809

    It is fixed in svn, so you can build 'geronimo-transaction' module
    locally or ignore the tests.

    Andrus


    On Feb 26, 2007, at 8:01 PM, Mike Kienenberger wrote:

    I'm now up to failing integration tests. You probably already know
    about these. I'll look up the skip tests command and let you know how
    it goes from there.


    -------------------------------------------------------
    T E S T S
    -------------------------------------------------------
    Running org.apache.cayenne.jpa.itest.ch5._5_4_EntityMnagerFactoryTest
    Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
    0.922 sec
    Running org.apache.cayenne.jpa.itest.ch5._5_5_1_JtaEntityManagerTest
    Apache OpenEJB 3.0-incubating-SNAPSHOT build: 20070224-02:26
    http://incubator.apache.org/openejb
    Cannot find the configuration file [conf/openejb.xml]. Creating
    one at C:\works
    paces\cayenne\cayenne-2007-02-24-2034\itests\jpa-chapter5\target
    \openejb-out\con
    f\openejb.xml
    OpenEJB ready.
    Will transform: org/apache/cayenne/jpa/itest/ch5/entity/SimpleEntity
    Tests run: 2, Failures: 1, Errors: 1, Skipped: 0, Time elapsed:
    2.015 sec <<< FA
    ILURE!
    Running
    org.apache.cayenne.jpa.itest.ch5._5_5_2_ResourceLocalEntityManagerTest
    Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
    0.094 sec

    Results :
    Tests run: 5, Failures: 1, Errors: 1, Skipped: 0

    [INFO]
    ----------------------------------------------------------------------
    --
    [ERROR] BUILD FAILURE
    [INFO]
    ----------------------------------------------------------------------
    --
    [INFO] There are test failures.
    [INFO]
    ----------------------------------------------------------------------
    --
    [INFO] For more information, run Maven with the -e switch
    [INFO]
    ----------------------------------------------------------------------
    --
    [INFO] Total time: 6 minutes 37 seconds
    [INFO] Finished at: Mon Feb 26 12:53:40 EST 2007
    [INFO] Final Memory: 26M/47M
    [INFO]
    ----------------------------------------------------------------------
    --
    On 2/26/07, Andrus Adamchik wrote:
    Fixed.
    On Feb 26, 2007, at 7:09 PM, Mike Kienenberger wrote:

    Here's the next error.

    [ERROR] BUILD ERROR
    [INFO]
    ---------------------------------------------------------------------
    -
    --
    [INFO] Failed to resolve artifact.

    Missing:
    ----------
    1) jgoodies:looks:jar:1.3.1

    Try downloading the file manually from the project website.

    Then, install it using the command:
    mvn install:install-file -DgroupId=jgoodies -
    DartifactId=looks \
    -Dversion=1.3.1 -Dpackaging=jar -Dfile=/path/to/file

    Path to dependency:
    1) org.apache.cayenne:cayenne-modeler:jar:3.0-SNAPSHOT
    2) jgoodies:looks:jar:1.3.1

    ----------
    1 required artifact is missing.

    for artifact:
    org.apache.cayenne:cayenne-modeler:jar:3.0-SNAPSHOT

    from the specified remote repositories:
    central (http://repo1.maven.org/maven2),
    apache-snapshots (http://people.apache.org/repo/m2-snapshot-
    repository/)


    [INFO]
    ---------------------------------------------------------------------
    -
    --
    [INFO] For more information, run Maven with the -e switch
    [INFO]
    ---------------------------------------------------------------------
    -
    --
    [INFO] Total time: 3 minutes 9 seconds
    [INFO] Finished at: Mon Feb 26 12:09:53 EST 2007
    [INFO] Final Memory: 16M/29M
    [INFO]
    ---------------------------------------------------------------------
    -
    --
    On 2/26/07, Mike Kienenberger wrote:
    :-)

    I think that makes the most sense as I suspect doc- and web-
    related
    dependencies are more fragile than regular code. At least, I've
    seen
    these things break more often in MyFaces than the standard library
    build tools.
    On 2/26/07, Andrus Adamchik wrote:
    Sure we can split the plugin, and put the docs mojo in the docs
    folder. Yet another module to maintain ;-)

    On Feb 26, 2007, at 6:55 PM, Mike Kienenberger wrote:
    But isn't the whole point of using maven that this various
    modules can
    be built independently, provided the minimal dependencies are
    met?
    I don't think something like the web site (which a regular
    cayenne
    user doesn't need) should be a dependency of the runtime/
    modeler.
    On 2/26/07, Andrus Adamchik wrote:
    They part of the same custom build plugin. Of course we can
    split it
    in multiple small plugins, but then the maintenance would
    become much
    harder.

    Andrus
    On Feb 26, 2007, at 6:19 PM, Mike Kienenberger wrote:
    On 2/26/07, Andrus Adamchik wrote:
    Done, please try again.
    Ok. I have new probably-unrelated errors (next message). However,
    it seems odd to me that the dependencies for building the
    web site
    would block the rest of the cayenne build. Is this
    something
    we can
    fix down the road?
  • Mike Kienenberger at Feb 26, 2007 at 7:39 pm
    Second run took 17 minutes. So did a "mvn clean" (minute and a half)
    followed by a "mvn" (another 17 minutes).

    I'm hoping/guessing that a lot of this is due to checking versions
    over the internet. I vaguely recall that there's a way to maybe
    surpress this behavior.

    On 2/26/07, Mike Kienenberger wrote:
    Ok. Finally built it. Build time 16 minutes and 32 seconds, with
    skip-tests enabled. I'm going to do another build to see if this was
    still downloading dependencies in the last build.
    On 2/26/07, Andrus Adamchik wrote:
    Yep - this is due to a bug in Geronimo TX manager:

    https://issues.apache.org/jira/browse/GERONIMO-2809

    It is fixed in svn, so you can build 'geronimo-transaction' module
    locally or ignore the tests.

    Andrus


    On Feb 26, 2007, at 8:01 PM, Mike Kienenberger wrote:

    I'm now up to failing integration tests. You probably already know
    about these. I'll look up the skip tests command and let you know how
    it goes from there.


    -------------------------------------------------------
    T E S T S
    -------------------------------------------------------
    Running org.apache.cayenne.jpa.itest.ch5._5_4_EntityMnagerFactoryTest
    Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
    0.922 sec
    Running org.apache.cayenne.jpa.itest.ch5._5_5_1_JtaEntityManagerTest
    Apache OpenEJB 3.0-incubating-SNAPSHOT build: 20070224-02:26
    http://incubator.apache.org/openejb
    Cannot find the configuration file [conf/openejb.xml]. Creating
    one at C:\works
    paces\cayenne\cayenne-2007-02-24-2034\itests\jpa-chapter5\target
    \openejb-out\con
    f\openejb.xml
    OpenEJB ready.
    Will transform: org/apache/cayenne/jpa/itest/ch5/entity/SimpleEntity
    Tests run: 2, Failures: 1, Errors: 1, Skipped: 0, Time elapsed:
    2.015 sec <<< FA
    ILURE!
    Running
    org.apache.cayenne.jpa.itest.ch5._5_5_2_ResourceLocalEntityManagerTest
    Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
    0.094 sec

    Results :
    Tests run: 5, Failures: 1, Errors: 1, Skipped: 0

    [INFO]
    ----------------------------------------------------------------------
    --
    [ERROR] BUILD FAILURE
    [INFO]
    ----------------------------------------------------------------------
    --
    [INFO] There are test failures.
    [INFO]
    ----------------------------------------------------------------------
    --
    [INFO] For more information, run Maven with the -e switch
    [INFO]
    ----------------------------------------------------------------------
    --
    [INFO] Total time: 6 minutes 37 seconds
    [INFO] Finished at: Mon Feb 26 12:53:40 EST 2007
    [INFO] Final Memory: 26M/47M
    [INFO]
    ----------------------------------------------------------------------
    --
    On 2/26/07, Andrus Adamchik wrote:
    Fixed.
    On Feb 26, 2007, at 7:09 PM, Mike Kienenberger wrote:

    Here's the next error.

    [ERROR] BUILD ERROR
    [INFO]
    ---------------------------------------------------------------------
    -
    --
    [INFO] Failed to resolve artifact.

    Missing:
    ----------
    1) jgoodies:looks:jar:1.3.1

    Try downloading the file manually from the project website.

    Then, install it using the command:
    mvn install:install-file -DgroupId=jgoodies -
    DartifactId=looks \
    -Dversion=1.3.1 -Dpackaging=jar -Dfile=/path/to/file

    Path to dependency:
    1) org.apache.cayenne:cayenne-modeler:jar:3.0-SNAPSHOT
    2) jgoodies:looks:jar:1.3.1

    ----------
    1 required artifact is missing.

    for artifact:
    org.apache.cayenne:cayenne-modeler:jar:3.0-SNAPSHOT

    from the specified remote repositories:
    central (http://repo1.maven.org/maven2),
    apache-snapshots (http://people.apache.org/repo/m2-snapshot-
    repository/)


    [INFO]
    ---------------------------------------------------------------------
    -
    --
    [INFO] For more information, run Maven with the -e switch
    [INFO]
    ---------------------------------------------------------------------
    -
    --
    [INFO] Total time: 3 minutes 9 seconds
    [INFO] Finished at: Mon Feb 26 12:09:53 EST 2007
    [INFO] Final Memory: 16M/29M
    [INFO]
    ---------------------------------------------------------------------
    -
    --
    On 2/26/07, Mike Kienenberger wrote:
    :-)

    I think that makes the most sense as I suspect doc- and web-
    related
    dependencies are more fragile than regular code. At least, I've
    seen
    these things break more often in MyFaces than the standard library
    build tools.
    On 2/26/07, Andrus Adamchik wrote:
    Sure we can split the plugin, and put the docs mojo in the docs
    folder. Yet another module to maintain ;-)

    On Feb 26, 2007, at 6:55 PM, Mike Kienenberger wrote:
    But isn't the whole point of using maven that this various
    modules can
    be built independently, provided the minimal dependencies are
    met?
    I don't think something like the web site (which a regular
    cayenne
    user doesn't need) should be a dependency of the runtime/
    modeler.
    On 2/26/07, Andrus Adamchik wrote:
    They part of the same custom build plugin. Of course we can
    split it
    in multiple small plugins, but then the maintenance would
    become much
    harder.

    Andrus
    On Feb 26, 2007, at 6:19 PM, Mike Kienenberger wrote:
    On 2/26/07, Andrus Adamchik wrote:
    Done, please try again.
    Ok. I have new probably-unrelated errors (next message). However,
    it seems odd to me that the dependencies for building the
    web site
    would block the rest of the cayenne build. Is this
    something
    we can
    fix down the road?
  • Andrus Adamchik at Feb 27, 2007 at 9:02 am
    "mvn -o" does an offline build.

    Andrus

    On Feb 26, 2007, at 9:38 PM, Mike Kienenberger wrote:

    Second run took 17 minutes. So did a "mvn clean" (minute and a half)
    followed by a "mvn" (another 17 minutes).

    I'm hoping/guessing that a lot of this is due to checking versions
    over the internet. I vaguely recall that there's a way to maybe
    surpress this behavior.

    On 2/26/07, Mike Kienenberger wrote:
    Ok. Finally built it. Build time 16 minutes and 32 seconds, with
    skip-tests enabled. I'm going to do another build to see if this
    was
    still downloading dependencies in the last build.
    On 2/26/07, Andrus Adamchik wrote:
    Yep - this is due to a bug in Geronimo TX manager:

    https://issues.apache.org/jira/browse/GERONIMO-2809

    It is fixed in svn, so you can build 'geronimo-transaction' module
    locally or ignore the tests.

    Andrus


    On Feb 26, 2007, at 8:01 PM, Mike Kienenberger wrote:

    I'm now up to failing integration tests. You probably already
    know
    about these. I'll look up the skip tests command and let you
    know how
    it goes from there.


    -------------------------------------------------------
    T E S T S
    -------------------------------------------------------
    Running
    org.apache.cayenne.jpa.itest.ch5._5_4_EntityMnagerFactoryTest
    Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
    0.922 sec
    Running
    org.apache.cayenne.jpa.itest.ch5._5_5_1_JtaEntityManagerTest
    Apache OpenEJB 3.0-incubating-SNAPSHOT build: 20070224-02:26
    http://incubator.apache.org/openejb
    Cannot find the configuration file [conf/openejb.xml]. Creating
    one at C:\works
    paces\cayenne\cayenne-2007-02-24-2034\itests\jpa-chapter5\target
    \openejb-out\con
    f\openejb.xml
    OpenEJB ready.
    Will transform: org/apache/cayenne/jpa/itest/ch5/entity/
    SimpleEntity
    Tests run: 2, Failures: 1, Errors: 1, Skipped: 0, Time elapsed:
    2.015 sec <<< FA
    ILURE!
    Running
    org.apache.cayenne.jpa.itest.ch5._5_5_2_ResourceLocalEntityManagerTes
    t
    Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
    0.094 sec

    Results :
    Tests run: 5, Failures: 1, Errors: 1, Skipped: 0

    [INFO]
    ---------------------------------------------------------------------
    -
    --
    [ERROR] BUILD FAILURE
    [INFO]
    ---------------------------------------------------------------------
    -
    --
    [INFO] There are test failures.
    [INFO]
    ---------------------------------------------------------------------
    -
    --
    [INFO] For more information, run Maven with the -e switch
    [INFO]
    ---------------------------------------------------------------------
    -
    --
    [INFO] Total time: 6 minutes 37 seconds
    [INFO] Finished at: Mon Feb 26 12:53:40 EST 2007
    [INFO] Final Memory: 26M/47M
    [INFO]
    ---------------------------------------------------------------------
    -
    --
    On 2/26/07, Andrus Adamchik wrote:
    Fixed.
    On Feb 26, 2007, at 7:09 PM, Mike Kienenberger wrote:

    Here's the next error.

    [ERROR] BUILD ERROR
    [INFO]
    ---------------------------------------------------------------------
    -
    --
    [INFO] Failed to resolve artifact.

    Missing:
    ----------
    1) jgoodies:looks:jar:1.3.1

    Try downloading the file manually from the project website.

    Then, install it using the command:
    mvn install:install-file -DgroupId=jgoodies -
    DartifactId=looks \
    -Dversion=1.3.1 -Dpackaging=jar -Dfile=/path/to/file

    Path to dependency:
    1) org.apache.cayenne:cayenne-modeler:jar:3.0-SNAPSHOT
    2) jgoodies:looks:jar:1.3.1

    ----------
    1 required artifact is missing.

    for artifact:
    org.apache.cayenne:cayenne-modeler:jar:3.0-SNAPSHOT

    from the specified remote repositories:
    central (http://repo1.maven.org/maven2),
    apache-snapshots (http://people.apache.org/repo/m2-snapshot-
    repository/)


    [INFO]
    ---------------------------------------------------------------------
    -
    --
    [INFO] For more information, run Maven with the -e switch
    [INFO]
    ---------------------------------------------------------------------
    -
    --
    [INFO] Total time: 3 minutes 9 seconds
    [INFO] Finished at: Mon Feb 26 12:09:53 EST 2007
    [INFO] Final Memory: 16M/29M
    [INFO]
    ---------------------------------------------------------------------
    -
    --
    On 2/26/07, Mike Kienenberger wrote:
    :-)

    I think that makes the most sense as I suspect doc- and web-
    related
    dependencies are more fragile than regular code. At
    least, I've
    seen
    these things break more often in MyFaces than the standard
    library
    build tools.
    On 2/26/07, Andrus Adamchik wrote:
    Sure we can split the plugin, and put the docs mojo in
    the docs
    folder. Yet another module to maintain ;-)

    On Feb 26, 2007, at 6:55 PM, Mike Kienenberger wrote:
    But isn't the whole point of using maven that this
    various
    modules can
    be built independently, provided the minimal
    dependencies are
    met?
    I don't think something like the web site (which a
    regular
    cayenne
    user doesn't need) should be a dependency of the runtime/
    modeler.
    On 2/26/07, Andrus Adamchik <andrus@objectstyle.org>
    wrote:
    They part of the same custom build plugin. Of course
    we can
    split it
    in multiple small plugins, but then the maintenance
    would
    become much
    harder.

    Andrus
    On Feb 26, 2007, at 6:19 PM, Mike Kienenberger wrote:

    On 2/26/07, Andrus Adamchik
    wrote:
    Done, please try again.
    Ok. I have new probably-unrelated errors (next
    message).
    However,
    it seems odd to me that the dependencies for
    building the
    web site
    would block the rest of the cayenne build. Is this
    something
    we can
    fix down the road?
  • Michael Gentry at Feb 27, 2007 at 1:52 pm
    Doing "mvn -Dmaven.test.skip=true install" (after a previous "mvn
    clean"), I get:

    [INFO] ------------------------------------------------------------------------
    [INFO] BUILD SUCCESSFUL
    [INFO] ------------------------------------------------------------------------
    [INFO] Total time: 3 minutes 12 seconds
    [INFO] Finished at: Tue Feb 27 08:47:43 EST 2007
    [INFO] Final Memory: 33M/63M
    [INFO] ------------------------------------------------------------------------

    If I did this on my old PowerBook, though, it would be significantly
    slower. That probably doesn't help you at all. I also got bit by the
    integration test failures, so I just skip the tests for now.

    /dev/mrg

    On 2/27/07, Andrus Adamchik wrote:
    "mvn -o" does an offline build.

    Andrus

    On Feb 26, 2007, at 9:38 PM, Mike Kienenberger wrote:

    Second run took 17 minutes. So did a "mvn clean" (minute and a half)
    followed by a "mvn" (another 17 minutes).

    I'm hoping/guessing that a lot of this is due to checking versions
    over the internet. I vaguely recall that there's a way to maybe
    surpress this behavior.

    On 2/26/07, Mike Kienenberger wrote:
    Ok. Finally built it. Build time 16 minutes and 32 seconds, with
    skip-tests enabled. I'm going to do another build to see if this
    was
    still downloading dependencies in the last build.
    On 2/26/07, Andrus Adamchik wrote:
    Yep - this is due to a bug in Geronimo TX manager:

    https://issues.apache.org/jira/browse/GERONIMO-2809

    It is fixed in svn, so you can build 'geronimo-transaction' module
    locally or ignore the tests.

    Andrus


    On Feb 26, 2007, at 8:01 PM, Mike Kienenberger wrote:

    I'm now up to failing integration tests. You probably already
    know
    about these. I'll look up the skip tests command and let you
    know how
    it goes from there.


    -------------------------------------------------------
    T E S T S
    -------------------------------------------------------
    Running
    org.apache.cayenne.jpa.itest.ch5._5_4_EntityMnagerFactoryTest
    Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
    0.922 sec
    Running
    org.apache.cayenne.jpa.itest.ch5._5_5_1_JtaEntityManagerTest
    Apache OpenEJB 3.0-incubating-SNAPSHOT build: 20070224-02:26
    http://incubator.apache.org/openejb
    Cannot find the configuration file [conf/openejb.xml]. Creating
    one at C:\works
    paces\cayenne\cayenne-2007-02-24-2034\itests\jpa-chapter5\target
    \openejb-out\con
    f\openejb.xml
    OpenEJB ready.
    Will transform: org/apache/cayenne/jpa/itest/ch5/entity/
    SimpleEntity
    Tests run: 2, Failures: 1, Errors: 1, Skipped: 0, Time elapsed:
    2.015 sec <<< FA
    ILURE!
    Running
    org.apache.cayenne.jpa.itest.ch5._5_5_2_ResourceLocalEntityManagerTes
    t
    Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
    0.094 sec

    Results :
    Tests run: 5, Failures: 1, Errors: 1, Skipped: 0

    [INFO]
    ---------------------------------------------------------------------
    -
    --
    [ERROR] BUILD FAILURE
    [INFO]
    ---------------------------------------------------------------------
    -
    --
    [INFO] There are test failures.
    [INFO]
    ---------------------------------------------------------------------
    -
    --
    [INFO] For more information, run Maven with the -e switch
    [INFO]
    ---------------------------------------------------------------------
    -
    --
    [INFO] Total time: 6 minutes 37 seconds
    [INFO] Finished at: Mon Feb 26 12:53:40 EST 2007
    [INFO] Final Memory: 26M/47M
    [INFO]
    ---------------------------------------------------------------------
    -
    --
    On 2/26/07, Andrus Adamchik wrote:
    Fixed.
    On Feb 26, 2007, at 7:09 PM, Mike Kienenberger wrote:

    Here's the next error.

    [ERROR] BUILD ERROR
    [INFO]
    ---------------------------------------------------------------------
    -
    --
    [INFO] Failed to resolve artifact.

    Missing:
    ----------
    1) jgoodies:looks:jar:1.3.1

    Try downloading the file manually from the project website.

    Then, install it using the command:
    mvn install:install-file -DgroupId=jgoodies -
    DartifactId=looks \
    -Dversion=1.3.1 -Dpackaging=jar -Dfile=/path/to/file

    Path to dependency:
    1) org.apache.cayenne:cayenne-modeler:jar:3.0-SNAPSHOT
    2) jgoodies:looks:jar:1.3.1

    ----------
    1 required artifact is missing.

    for artifact:
    org.apache.cayenne:cayenne-modeler:jar:3.0-SNAPSHOT

    from the specified remote repositories:
    central (http://repo1.maven.org/maven2),
    apache-snapshots (http://people.apache.org/repo/m2-snapshot-
    repository/)


    [INFO]
    ---------------------------------------------------------------------
    -
    --
    [INFO] For more information, run Maven with the -e switch
    [INFO]
    ---------------------------------------------------------------------
    -
    --
    [INFO] Total time: 3 minutes 9 seconds
    [INFO] Finished at: Mon Feb 26 12:09:53 EST 2007
    [INFO] Final Memory: 16M/29M
    [INFO]
    ---------------------------------------------------------------------
    -
    --
    On 2/26/07, Mike Kienenberger wrote:
    :-)

    I think that makes the most sense as I suspect doc- and web-
    related
    dependencies are more fragile than regular code. At
    least, I've
    seen
    these things break more often in MyFaces than the standard
    library
    build tools.
    On 2/26/07, Andrus Adamchik wrote:
    Sure we can split the plugin, and put the docs mojo in
    the docs
    folder. Yet another module to maintain ;-)

    On Feb 26, 2007, at 6:55 PM, Mike Kienenberger wrote:
    But isn't the whole point of using maven that this
    various
    modules can
    be built independently, provided the minimal
    dependencies are
    met?
    I don't think something like the web site (which a
    regular
    cayenne
    user doesn't need) should be a dependency of the runtime/
    modeler.
    On 2/26/07, Andrus Adamchik <andrus@objectstyle.org>
    wrote:
    They part of the same custom build plugin. Of course
    we can
    split it
    in multiple small plugins, but then the maintenance
    would
    become much
    harder.

    Andrus
    On Feb 26, 2007, at 6:19 PM, Mike Kienenberger wrote:

    On 2/26/07, Andrus Adamchik
    wrote:
    Done, please try again.
    Ok. I have new probably-unrelated errors (next
    message).
    However,
    it seems odd to me that the dependencies for
    building the
    web site
    would block the rest of the cayenne build. Is this
    something
    we can
    fix down the road?

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupdev @
categoriescayenne
postedFeb 25, '07 at 7:50p
activeFeb 27, '07 at 1:52p
posts19
users3
websitecayenne.apache.org

People

Translate

site design / logo © 2022 Grokbase