On Feb 28, 2007, at 8:19 PM, Mike Kienenberger wrote:
I've updated the confluence page.
Hopefully others will review my guesses at the modules.
I also added my unresolved eclipse issues at the bottom of the page.
Nice start. Although the module categorization breakdown seems
arbitrary. I
Well, it's arbitrary because I had to guess what the modules were for :-)
Now that the structure is in place, could you take a couple of minutes
and correct the misconceptions (or the poor categorization) of the
modules? I think you are probably the most knowledgeable about it at
present.
On
I took a look at the svn folder layout.
- jpa-chapter-* and pojo are integration tests? Definitely not
obvious from the module names.
I also don't understand the difference between assemblies and build-tools.
I see both a modeler and a framework/cayenne-modeler directory.
I see
I'm sure it's a matter of
perspective.
No, it's a matter of Maven :).
So much about maven helps a better project organization.
Looking at the many mavenized projects I see no better organization,
but a higher fragmentation (very high for some projects).
Most of the time, this fragmentation is
Ahmed,
We are all in agreement that Maven is lacking. What we need is
either to improve it (via patches/discussion) or provide an
alternative (ant tasks). Provide some reasonable alternatives in the
form of patches, and I'll commit them.
On 3/1/07, Ahmed Mohombe [EMAIL PROTECTED] wrote:
Believe it or now the structure is pretty well thought out. It may
not be obvious, but documentation should help with this.
On Mar 1, 2007, at 6:47 PM, Mike Kienenberger wrote:
I took a look at the svn folder layout.
- jpa-chapter-* and pojo are integration tests? Definitely not
obvious
On Feb 28, 2007, at 7:07 AM, Mike Kienenberger wrote:
Strangely enough, the mvn -Dmaven.test.skip=true install only took 7
minutes this time instead of 17.
I optimized a build a bit further:
* Split the docs Mojo in a separate plugin, so there is no more
attempts to download Axis pom from
On Feb 28, 2007, at 7:07 AM, Mike Kienenberger wrote:
The remaining errors all deal with EJBQL, specifically in
cayenne-jdk1.4-unpublished/target/generated-sources in a default
package.
EJB parser is new... I just saw the same problem today as well. What
I did is reverted the .classpath
[EMAIL PROTECTED] wrote:
Using Eclipse with Mavenized Cayenne - http://cayenne.apache.org/
eclipse.html
Unfortunately this page needs some details.
==
# Get code from Subversion and build it from command line to seed the
local repository.
# Create two workspaces
Yes, I figured as much -- deleting everything in
cayenne-jdk1.4-unpublished/target/generated-sources got rid of the
errors and didn't seem to impact anything else.
On 2/28/07, Andrus Adamchik [EMAIL PROTECTED] wrote:
On Feb 28, 2007, at 7:07 AM, Mike Kienenberger wrote:
The remaining errors
Well, unfortunately, it didn't work out.
My eclipse projects are still messed up, whether fixed with
eclipse:clean and svn update or removing each of the files manually
and svn update.
At this point, I'm going to start over from scratch.
On 2/28/07, Mike Kienenberger [EMAIL PROTECTED] wrote:
I
Ok. Everything now looks good in the jdk15 workspace except for the
regression tests (expected it to fail) and the tutorials (which
probably shouldn't be failing -- we just need to fix the
dependencies).
The one issue I see with the maven2 dependencies is that there's no
javasource attached to
introduced...)
On 2/27/07, Mike Kienenberger [EMAIL PROTECTED] wrote:
Using Eclipse with Mavenized Cayenne - http://cayenne.apache.org/eclipse.html
Unfortunately this page needs some details.
==
# Get code from Subversion and build it from command line to seed the
local
13 matches
Mail list logo
