Mike, I think you've already past this point, but let me still
comment...
* Do not run "mvn eclipse:eclipse", as it is incompatible with the
maven plugin. Besides we have .classpath and .project files in all
projects that are being actively developed.
* M2_REPO is not needed; Maven plugin u
Ari,
An Apache UNIX account has been created for you (I think you
should've probably received a separate email about that). I set it up
with SVN write access to Cayenne project. I guess one last thing we
need to do is to update the web site and the Maven pom files,
reflecting your committ
May be you can participate the discussions too. ;)
I will at least watch it - I am on Geronimo dev list.
Andrus
On Feb 27, 2007, at 6:54 PM, Lasantha Ranaweera wrote:
Thanks Andrus for your explanation... I will investigate this more
bit &
create a patch pretty soon. We will try to get so
On Feb 28, 2007, at 7:07 AM, Mike Kienenberger wrote:
I started a jdk15 workspace and imported everything. 325 errors.
Closing cayenne-regression-profiler dropped it down to 129. I don't
think this code is currently maintained, is it?
yes, you probably shouldn't import this project.
Closi
On 28/02/2007, at 7:41 PM, Andrus Adamchik wrote:
An Apache UNIX account has been created for you (I think you
should've probably received a separate email about that). I set it
up with SVN write access to Cayenne project. I guess one last thing
we need to do is to update the web site and
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 fro
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 fil
Hi Andrus,
I am getting following error. Please find the attached pom.xml file too.
Anything I am missing?
Error = >
[INFO]
[ERROR] BUILD ERROR
[INFO]
--
Hi Andrus,
I am getting following error. Please find the attached pom.xml file too.
Anything am I missing?
Error = >
[INFO]
[ERROR] BUILD ERROR
[INFO]
--
Ok. That's my problem. I did mvn eclipse:eclipse. I wonder how I
can undo it?
Can we either disable or change the behavior of this command if it
doesn't work as expected? This is the first thing a Maven user is
going to try to do to get the project to work in Eclipse.At
minimum, the web
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 erro
In MyFaces, we typically have the new committer make these changes.
This gives them something simple to change while verifying that
everything is working for them.
On 2/28/07, Andrus Adamchik <[EMAIL PROTECTED]> wrote:
Ari,
An Apache UNIX account has been created for you (I think you
should've
My bad. Just deployed the parent POM to the repo. Let me know if you
see more errors.
Andrus
On Feb 28, 2007, at 3:11 PM, Lasantha Ranaweera wrote:
Hi Andrus,
I am getting following error. Please find the attached pom.xml file
too. Anything I am missing?
Error = >
[INFO]
On Feb 28, 2007, at 4:29 PM, Mike Kienenberger wrote:
Ok. That's my problem. I did mvn eclipse:eclipse. I wonder how I
can undo it?
rm .classpath .project
svn up
Can we either disable or change the behavior of this command if it
doesn't work as expected? This is the first thing a Mav
I started deleting these by hand, and then had an idea ---
mvn eclipse:clean
I think it worked, but it's hard to tell :-)
On 2/28/07, Andrus Adamchik <[EMAIL PROTECTED]> wrote:
On Feb 28, 2007, at 4:29 PM, Mike Kienenberger wrote:
> Ok. That's my problem. I did mvn eclipse:eclipse. I
Is maven-cayenne-build-plugin supposed to be 1.4 compatible?
If so, there's one error that prevents this:
maven-cayenne-build-plugin/src/main/java/org.apache.cayenne.maven.plugin.confluence/DocPageRenderer.java:line
219 has
matcher.appendReplacement(replacementBuffer,
matcher.group(0
On Feb 28, 2007, at 5:12 PM, Mike Kienenberger wrote:
Is maven-cayenne-build-plugin supposed to be 1.4 compatible?
If so, there's one error that prevents this:
Please update - i refactored the 1.5 part to maven-cayenne-doc-
plugin. Besides you probably don't need this module in Eclipse at
a
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:
If I ever get a useable version of Cayenne into Eclipse, I'll give it a shot.
So far, two days later, it's not looking hopeful. :-)
On 2/28/07, Andrus Adamchik <[EMAIL PROTECTED]> wrote:
On Feb 28, 2007, at 5:12 PM, Mike Kienenberger wrote:
> Is maven-cayenne-build-plugin supposed to be 1.4 c
I can feel your pain. I didn't have any problems specifically with
Eclipse, but the builds do break often. To access the bulk of the
code you just need one or more of these modules in Eclipse. They can
be imported one at a time in any order. Don't waste your time on
importing the build plug
I'm still importing, so it's too soon to tell.
Yes, I know that the builds can break, although I would hope our core
modules (cayenne runtime & modeler) would be stable by this point,
with no checkins breaking compilability. I expecdt JPA to be in a
state of flux at present and don't necessarily
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 t
On Feb 28, 2007, at 6:35 PM, Mike Kienenberger wrote:
In fact, I'd like to see an enumeration of each module with a
description of
what it does and how it fits in to the big picture.
+1
No doubt there's
a maven plugin somewhere that will do this automatically :-)
No!!! Can we please do
On Feb 28, 2007, at 6:35 PM, Mike Kienenberger wrote:
> In fact, I'd like to see an enumeration of each module with a
> description of
> what it does and how it fits in to the big picture.
> No doubt there's
> a maven plugin somewhere that will do this automatically :-)
On 2/28/07, Andrus Adamc
I noticed that there's no svn attached to the eclipse projects. Did
I misconfigure it somehow?
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.
26 matches
Mail list logo
