Oh, maybe... I was watching this thread... lemme peek, I get way to
much email :-(
Cool. Thanks Brett.
--jason
On 12/12/06, Brett Porter <[EMAIL PROTECTED]> wrote:
Yeah, but you should have seen the update on jira when I closed it.
Anyway, I closed it.
- Brett
On 13/12/2006, at 5:39 PM,
Yeah, but you should have seen the update on jira when I closed it.
Anyway, I closed it.
- Brett
On 13/12/2006, at 5:39 PM, Jason Dillon wrote:
Last reply I got from you was the "i've got 4 more days"
--jason
On Dec 12, 2006, at 8:41 PM, Brett Porter wrote:
erm, didn't I apply it already
Last reply I got from you was the "i've got 4 more days"
--jason
On Dec 12, 2006, at 8:41 PM, Brett Porter wrote:
erm, didn't I apply it already?
On 13/12/2006, at 12:59 PM, Jason Dillon wrote:
So, no love?
Its okay... maybe when you have time take a peek... :-\
--jason
On Dec 5, 2006,
Are there any places I can go to find out more about maven-metadata.xml?
See http://www.nabble.com/forum/ViewPost.jtp?post=7845254&framed=y&skin=177
The problem is that the patched plugins, e.g. surefire or eclipse, are
resolving to the internal repository version number but then
attempting to c
On 12/12/06, Brett Porter <[EMAIL PROTECTED]> wrote:
Sorry, can't reproduce this with maven-2.0.5-SNAPSHOT on either Mac
or Windows.
Got any more information?
John and Jesse worked this out on IRC. Maven 2.0.5-snap orders
dependencies differently than 2.0.4. In 2.0.4, with multiple versions
For what it's worth, I've been working my way through getting the
latest Xerces artifacts uploaded, but new XML commons, resolver, and
the Xalan serializer need to be uploaded as well. I'm working through
all the various POMs and trying to populate them with as much
information as possible.
-Nath
Sorry, can't reproduce this with maven-2.0.5-SNAPSHOT on either Mac
or Windows.
Got any more information?
- Brett
On 07/12/2006, at 3:39 PM, Jesse McConnell wrote:
ya, if you look through her debug output there is a big chunk where
all the 2.0.4 deps are getting reverted to 2.0 just like in
erm, didn't I apply it already?
On 13/12/2006, at 12:59 PM, Jason Dillon wrote:
So, no love?
Its okay... maybe when you have time take a peek... :-\
--jason
On Dec 5, 2006, at 2:16 PM, Brett Porter wrote:
I've got 4 more days! :)
On 06/12/2006, at 9:12 AM, Jason Dillon wrote:
Ever get
On 12/13/06, Rahul Thakur <[EMAIL PROTECTED]> wrote:
If i remember correct from what I saw in the m-e-p sources last week,
maven-eclipse-plugin-test is created by the Plugin unit tests and then
installed to a *test* repo local to the Eclipse project.
Not sure why is your build seeing the -test v
If i remember correct from what I saw in the m-e-p sources last week,
maven-eclipse-plugin-test is created by the Plugin unit tests and then
installed to a *test* repo local to the Eclipse project.
Not sure why is your build seeing the -test version. Do you have
maven-eclipse-plugin sources ch
So, no love?
Its okay... maybe when you have time take a peek... :-\
--jason
On Dec 5, 2006, at 2:16 PM, Brett Porter wrote:
I've got 4 more days! :)
On 06/12/2006, at 9:12 AM, Jason Dillon wrote:
Ever get a chance?
--jason
On Dec 1, 2006, at 3:02 PM, Brett Porter wrote:
I'll look at
Manually hacking the jar to set the version correctly resolves the problem.
Now to find out why the jar is being created incorrectly...
Running mvn package will incorrectly create a "test" version for the
real version jar.
I just noticed that there are two jars in here:
* maven-eclipse-plugin
!/META-INF/maven/plugin.xml
Internal release from subversion revision r485327.
Applied patches:
* http://jira.codehaus.org/browse/MECLIPSE-206
* parent version now 4 instead of 4-SNAPSHOT
org.apache.maven.plugins
maven-eclipse-plugin
test
[del]
My pom version is:
2.3-INTE
Starting to get somewhere.
Running mvn in debug mode so I can attach eclipse to the running instance.
One thing I am noticing is that the attached sources don't match
exactly what is being run by maven. The eclipse plugin defines the
dependency on version 2.0.1 but I think the version being used
I have created a junk Mojo to spit out debug to see if I can see whats wrong.
This junk mojo works fine when run within the module (as expected).
When run in a reactor build this junk mojo is executed for the root
project but when when it attempts to go into a module it then fails
with the same e
I'll tell you if I can fix it with -Djava.awt.headless=true in MAVEN_OPTS
Arnaud
On 12/11/06, Lukas Theussl <[EMAIL PROTECTED]> wrote:
That reminds me of something...
http://jira.codehaus.org/browse/MPCLOVER-54
Never got any feedback though, so I don't know if/how it was resolved.
-Lukas
On 12/11/06, Brett Porter <[EMAIL PROTECTED]> wrote:
/export/home/continuum/public_html/maven-1.x/builds
I have to modify the bootstrap because it seems to use the MAVEN_HOME and I
can't override it.
I'll give you group admin rights so you can add an ant project. But
that's another bug :)
--- maven/plugins/trunk/pom.xml (original)
+++ maven/plugins/trunk/pom.xml Mon Dec 11 17:47:14 2006
@@ -66,7 +66,7 @@
apache.website
- scp://people.apache.org/www/maven.apache.org/plugins/url>
+ scp://people.apache.org/www/maven.apache.org/plugins/$
{pom.artifactId}/${v
On 12/11/06, Brett Porter <[EMAIL PROTECTED]> wrote:
I can give you an account if you want to try, I've no inclination to
myself :)
ok, let's go for it ;-) I already did it some times ago.
Doesn't -Djava.awt.headless=true work? This seems like a serious
oversight in the clover plugin. Plen
And that the failure is only for reactor builds.
Running in the modules themselves works fine.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
It's odd that mvn eclipse:clean works, but eclipse:eclipse does not...
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
See http://jira.codehaus.org/browse/MECLIPSE-192
I also see these messages with similar problems:
* http://www.mail-archive.com/users@maven.apache.org/msg56535.html
I'm running mvn eclipse:eclipse (with an internal release of the
snapshot version)
And I get a build failure like:
[INFO] Failed t
On 12/11/06, Lukas Theussl <[EMAIL PROTECTED]> wrote:
If we fix all backward compat problems then there is no reason for
anyone to use a new plugin with an old release of maven...
I'm completely agreed ;-)
The artifact plugin should be released for RC1, as it contains the fix
for MPARTIFAC
That didn't work. Here is my addition to server.xml:
type="javax.sql.DataSource">
maxWait
5000
maxActive
4
password
url
jdbc:derby:target/database/continuum
As a workaround - can you try moving the config from
continuum.xml to server.xml under global resoures (just like mentioned
on that thread). Pretty sure I have seen similar errors with JNDI
resource look ups in tomcat, but can't remember the solution off hand.
Cheers,
Rahul
Stephen Pietr
On 12/12/06, Rahul Thakur <[EMAIL PROTECTED]> wrote:
Hi,
Is anyone else noticing that Eclipse code style formatter is formatting
Java sources differently? Is anyone able to verify that the codestyle
preferences available from the site are sane or update if required. I
downloaded the preferences
I hadn't seen that thread. Thanks for the pointer to it.
I do get same message that the originator of that thread gets:
---
2006-12-12 14:20:31,590 [http-8080-Processor23] INFO
PlexusContainer- Loading on start [role]:
[org.apache.maven.continuum.Continuum]
2006-12-12
you can ping xerces mailing list and repository@apache.org
On 12/12/06, nicolas de loof <[EMAIL PROTECTED]> wrote:
According to http://xerces.apache.org/xerces2-j/, 2.9.0 is the latest stable
version of Xerces.
Why isn't it available on maven public repo ? Doesn't all apache projects
get automat
See comment inline...
[EMAIL PROTECTED] wrote:
Author: joakime
Date: Mon Dec 11 17:47:14 2006
New Revision: 485976
URL: http://svn.apache.org/viewvc?view=rev&rev=485976
Log:
Parameterizing the staging profile.
Modified:
maven/plugins/trunk/pom.xml
Modified: maven/plugins/trunk/pom.xml
URL
We use 4 digit build numbers and I never noticed it. Probably because we
control our versions very carefully and maven doesn't have to figure it
out for us. This could be an issue though.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carlos
Sanchez
Sent
Jason van Zyl wrote:
On 12 Dec 06, at 7:24 AM 12 Dec 06, nicolas de loof wrote:
According to http://xerces.apache.org/xerces2-j/, 2.9.0 is the latest
stable
version of Xerces.
Why isn't it available on maven public repo ? Doesn't all apache projects
get automatically sync with repo ?
No. I
On 12 Dec 06, at 7:24 AM 12 Dec 06, nicolas de loof wrote:
According to http://xerces.apache.org/xerces2-j/, 2.9.0 is the
latest stable
version of Xerces.
Why isn't it available on maven public repo ? Doesn't all apache
projects
get automatically sync with repo ?
No. It is not our respo
According to http://xerces.apache.org/xerces2-j/, 2.9.0 is the latest stable
version of Xerces.
Why isn't it available on maven public repo ? Doesn't all apache projects
get automatically sync with repo ?
Nico.
On 12 Dec 06, at 4:18 AM 12 Dec 06, Tom Huybrechts wrote:
On 12/12/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
This message (1) on pde-build-dev contains the state resolver as an
attachment. I used this to calculate access rules for the JDT
compiler, and to generate POMs for bundles.
http://d
some time ago I made all poms created by install-files extend a common
"eclipse" parent pom, with all the common info, Fabrizio reverted it.
On 12/11/06, Barrie Treloar <[EMAIL PROTECTED]> wrote:
> > > did you finally remove the usage of a parent pom for install-files?
> > > that made it easier
I just discovered MECLIPSE-172 about this.
Is there any plan to include it into maven-eclipse-plugin 2.3 ?
Nico.
2006/12/12, nicolas de loof <[EMAIL PROTECTED]>:
Hello,
The eclipse plugin allows to set custom classpathContainer. It will force
"org.eclipse.jdt.launching.JRE_CONTAINER" in this
Hello,
The eclipse plugin allows to set custom classpathContainer. It will force "
org.eclipse.jdt.launching.JRE_CONTAINER" in this list if not set (with a
warning).
I have a use case to set the target environment in my application modules
for warious JRE. I'm using the JRE container string :
"
On 12/11/06, Fabrizio Giustina <[EMAIL PROTECTED]> wrote:
- the 4th token MUST be separated with "-" in maven, while in osgi
MUST be "." (this is handled by the make-artifacts goal actually). A
version like 1.2.3-4 in maven is parsed as [major 1, minor 2, patch 3,
build 4], a version like 1.2.3.4
On 12/12/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On 11 Dec 06, at 10:25 PM 11 Dec 06, Scott Lewis wrote:
> Hi Jason,
>
>
> What is the State resolver?
Dependency resolver. Basically a state machine that consumes OSGi
dependency information, determines what's missing and asks for more.
How
Hi,
Is anyone else noticing that Eclipse code style formatter is formatting
Java sources differently? Is anyone able to verify that the codestyle
preferences available from the site are sane or update if required. I
downloaded the preferences just a couple of days ago.
Can we also update the
40 matches
Mail list logo
