sues but I don't see how we can completely switch
geronimo to m2 without this.
thanks
david jencks
Thanks
--
Jeremy
Jeremy Boynes (JIRA) wrote:
Add LICENCE and NOTICE files to the jar
---
Key: MJAR-42
URL: http://jira.codehaus.org
situation occurring for the new xmlbeans release. I'll try to come
up with something correct in the next few days but meanwhile I'd like
to know what can be done to prevent broken poms from being deployed,
especially for this particular case.
maven really to force any such project to split the
build up into at least two phases, the first where the stuff the
plugin uses is built + the plugin, the second the stuff that uses the
plugin? To me this seems like close to a showstopper for using maven.
thanks
david jencks
m an unknown source, is wrong, did not come from the
project, and can't be updated. Much as I like maven it's hard for me
to see how this is going to lead to success.
thanks
david jencks
It also may seem ideal to have projects take care of their own POMs,
but it makes it frustratin
On Jul 4, 2006, at 6:33 PM, Brett Porter wrote:
On 5/07/2006 10:54 AM, David Jencks wrote:
I think the process is somewhat broken and that the maven team is
being far too strict about changing broken poms that were in fact
installed by the maven team, not supplied by the project
en.plugin.ear.EarModule]
So what am I missing? How come that 'isInstance' method from the Class
object could return different results?
The classes are in different classloaders. Hopefully the
classloaders' toString() will give you enough info about which ones
they are if you a
cache and the other plugins
are not getting reloaded.
Can anyone suggest a way to produce a reliable build with the current
plugin releases? We might be able to restrict ourselves to 1.1-b2.
Will the proposed 1.7 plugin-plugin release help with this problem?
thanks
da
commit a version in some other project that will be using it (such as
geronimo or openejb)?
thanks
david jencks
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
e url tag for purposes of automated download would break
its current function of letting people answer the question, "What does
this do, anyway?"
I fear that adding a second way to obtain artifacts will result in
wholesale confusion.
than
Is there any chance of getting the rar plugin I submitted in before the
1.0 release?
http://jira.codehaus.org/browse/MAVEN-1301
thanks
david jencks
On Saturday, June 12, 2004, at 09:37 PM, Brett Porter wrote:
Hi all,
I anticipate being ready to vote for Maven 1.0 within a week now, and
need to
nerated-sources/xdoclet/java
/target/generated-sources/xdoclet/ejb
thanks
david jencks
and they would each be a source folder in Eclipse. Works great.
However,
because maven.gen.src is defined in the Eclipse plugin only, you have
to
specify for the hibernate and xdoclet plugins the full path to
Although Dion very kindly committed the original rar plugin, since you
wish to be lead of all the other j2ee artifact generating plugins, it
might make sense for you to take that one as well.
BTW all suggestions for improvements would be welcome:-)
thanks
david jencks
On Friday, July 23, 2004
If no one can actually fix your problem, you can always build the
adapter jar in one project and package it into the rar in another, with
slightly different names. I would definitely prefer that someone
figure out how to have multiple dependencies such as you ask for.
thanks
david jencks
On
l project, and links dependencies that are not
in the multiproject build as jar dependencies in the repo. Does the
eclipse plugin do this? Is this related to this discussion?
thanks
david jencks
On Sep 24, 2004, at 8:10 AM, Jörg Schaible wrote:
Eric Pugh wrote on Friday, September 24, 2004 4:07 PM:
dds target/xmlbeans to the idea sources.
This is similar to what the eclipse plugin does.
See http://jira.codehaus.org/browse/MPIDEA-10
thanks
david jencks
On Sep 24, 2004, at 1:08 AM, Alex Karasulu wrote:
Hiya,
I've been playing with the idea plugin to see if I can get it to
include
the antlr
its value with Build and Project
and working downwards, but get the same result.
What can cause this behavior?
thanks
david jencks
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
classloading difficulties for multiple plugin versions in 1.0.2
thanks
david jencks
On Jul 10, 2005, at 11:56 AM, David Jencks wrote:
I'm working with a jelly bean in a plugin in maven 1.0.2.
It has a property I am setting thusly in plugin.jelly:
reso
Hogstrom: matt at hogstrom.org
I think the build is mavenized, but I'm not sure.
thanks
david jencks
On Aug 23, 2005, at 2:52 AM, Vincent Massol wrote:
-Original Message-
From: Thomas Van de Velde [mailto:[EMAIL PROTECTED]
Sent: mardi 23 août 2005 11:46
To: Maven Developers
OS9 supports 1.1 at most. It certainly never got close to 1.3. I don't
think you can use that as an argument against requiring 1.4 :-)
david jencks
On May 1, 2005, at 1:37 PM, Thomas Van de Velde wrote:
I think Mac OS9 only supports jdk 1.3 but I guess nobody is using that.
Thomas
On 5
results are
obvious, and are the pro or anti java 21 folks starting the haggling?
thanks
David Jencks
> On May 23, 2025, at 1:05 PM, Gary Gregory wrote:
>
> There is an interesting parallel here with the what is happening in the
> logo-dev mailing list: Someone calls for a vote, the
ObjectWeb HOWL pom
--
Key: MEV-196
URL: http://jira.codehaus.org/browse/MEV-196
Project: Maven Evangelism
Type: Task
Components: Missing POM
Reporter: David Jencks
This is a valid m2 pom that is checked into the howl repo. However, AFAICT
[ http://jira.codehaus.org/browse/MEV-196?page=all ]
David Jencks updated MEV-196:
-
Attachment: pom.xml
This is the actual pom rather than a diff, since it is a new file.
> ObjectWeb HOWL pom
> --
>
> Key: MEV-196
&g
[ http://jira.codehaus.org/browse/MAVEN-1634?page=comments#action_41996 ]
David Jencks commented on MAVEN-1634:
-
I fixed the backtick and some syntax errors in several project.xml's
Now I'
[ http://jira.codehaus.org/browse/MNG-581?page=comments#action_42733 ]
David Jencks commented on MNG-581:
--
Just including the generated classes in target/classes seems to be adequate for
m1. I think a fix for this is needed in m2. To me asking xmlbeans
[ http://jira.codehaus.org/browse/MEV-48?page=comments#action_43741 ]
David Jencks commented on MEV-48:
-
These are antique milestone releases that we aren't planning to ever look at
again. G1M4 should be out in a day or two and it uses a different w
[ http://jira.codehaus.org/browse/MNG-699?page=comments#action_45803 ]
David Jencks commented on MNG-699:
--
I have no particular opinion on the idea of allowing you to change the
extension of the artifact generated by the jar plugin, but would like to point
[ http://jira.codehaus.org/browse/MEV-8?page=comments#action_39773 ]
David Jencks commented on MEV-8:
Since there are non-sun freely available implementations of many of these specs
I would prefer to see the provenance (Sun) for these particular
101 - 127 of 127 matches
Mail list logo