On 6/07/2006 1:32 AM, jerome lacoste wrote:
- they typically use a versionning similar to x.y.z-n sometimes
adding. -n can be used to fix packaging issues (POM in the case of
maven). Vendor fixes are also accepted and version names reflect the
vendor name.
Yep, already have that for that very r
Hi Brett,
Brett Porter wrote on Friday, July 07, 2006 8:49 AM:
> On 6/07/2006 3:40 AM, Rinku wrote:
[snip]
>> The other thing is that when an artifact is published to a repo, the
>> publisher can add some compatibility meta-data as well to indicate
>> that the current version is incompatible with
On 7/7/06, Brett Porter <[EMAIL PROTECTED]> wrote:
Thanks, I thought NB had already changed to that requirement (Eclipse
and IDEA have some time ago).
it did update, however right at the beginning of the next release
cycle (6.0) which is a month or two back. Nb has the policy of
supporting 2 st
On 6/07/2006 3:40 AM, Rinku wrote:
Just wondering if rather than having an list stuffed in each
of elements, if we could have some sort of
tag that can 'advise' Maven the choosing strategy for conflicting
artifacts (pretty much like version ranges).
For sake of an example:
I think we need a specific (past) version of the plugins in use in the
parent (it used to work with the plugin-plugin, so this must be possible).
I think we should omit the changelog plugin from the proposed doc
standard and the pom for now.
- Brett
On 7/07/2006 5:24 AM, jerome lacoste wrote
I've applied and published this version. I still had further comments,
but it's a definite improvement (draft2 was applied before the last
release - we'll have a 2.0.2 soon to rectify this and other problems).
Thanks Pete!
Cheers,
Brett
On 7/07/2006 10:08 AM, Pete Marvin King wrote:
hello
Currently, I use Netbeans with jdk 1.4 at work (but no Maven) and with
5.0at home.
Raphaël
2006/7/7, Brett Porter <[EMAIL PROTECTED]>:
Thanks, I thought NB had already changed to that requirement (Eclipse
and IDEA have some time ago).
Do you have any indication of how many NB users stick to o
This is a good alternative. I think it should be added to the
documentation (both approaches should be documented).
Can you provide a patch?
Thanks,
Brett
On 5/07/2006 5:33 PM, Nicolas De Loof wrote:
I've read on
http://maven.apache.org/plugins/maven-compiler-plugin/howto.html
the "officia
+1, pending the resolution of MPMD-36 (pom packaging, could be a won't
fix) and MPMD-34 (docs have one failure in docck).
One thing to watch out for - currently the parent is plugin parent
2-SNAPSHOT. We might need to either release that (setting the
plugin-plugin report to latest and just ens
+0
Definitely want these, but I was really waiting until traffic demanded
it, as there's none on here at the moment. Is this primarily about
separating the commits?
The one thing I wanted to avoid was the initial ghost town of empty
lists when we're trying to kick it along (even if there isn
Thanks, I thought NB had already changed to that requirement (Eclipse
and IDEA have some time ago).
Do you have any indication of how many NB users stick to old versions? I
get the feeling they upgrade pretty fast. I'd also be interested to see
how many NB users still use JDK 1.4 to run the ID
how about setting up the repository manager somewhere? :)
+1 on the lists.
Milos
On 7/7/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
Hi,
How about we setup some lists for the repository manager?
Jason van Zyl
[EMAIL PROTECTED]
-
+1
Fabrice.
On 7/6/06, Mike Perham <[EMAIL PROTECTED]> wrote:
I think PMD is in good shape. We've upgraded to PMD 3.7, added a bunch
of tests and upgraded the documentation. Can someone tell me how to run
the docck checker so I can verify the docs before publishing the site?
The RC snapshot
-1
for netbeans integration that would probably mean dropping 5.0 and
upcoming 5.5 support, as only the cvs trunk of netbeans switched to
jdk15. we could maybe try to make sure people start the IDE with 1.5.
I have no experience with such setup though, would it work?
Milos
On 7/7/06, Brett Port
I'm sure that most organizations with a central build system will have
little problem using Java 5, the only danger I see in my group is individual
developers who like to run builds locally using Maven, when we develop with
1.4. They must continue developing in 1.4, and now requre 5 soley for Mave
Just wondering, I'm not familiar with eclipse sourcebase.
If maven uses some eclipse APIs, thus using some eclipse binaries in
non-eclipse way (no osgi/plugin encapsulation) and then we use the
maven binaries in an eclipse plugin, can we get in trouble? (by having
2 versions of same binaries on c
Issue Subscription
Filter: Design & Best Practices (37 issues)
Subscriber: mavendevlist
Key Summary
MNG-2184Possible problem with @aggregator and forked lifecycles
http://jira.codehaus.org/browse/MNG-2184
MNG-612 implement conflict resolution techniques
htt
Yep, that's what I meant. It's something we should have regardless, but
would be an absolute prerequisite to moving Maven over.
On 7/07/2006 11:51 AM, Stephen Duncan wrote:
While I'm happily developing use Java 5 now, what would be the impact
on those needing to target Java 1.4 or below buildin
While I'm happily developing use Java 5 now, what would be the impact
on those needing to target Java 1.4 or below building with Maven?
Specifically, the relative ease/difficulty of making sure to compile
against the 1.4 JDK libraries? Is that meant to be covered under
"improved support for invok
Hi,
I wanted to get thoughts on starting to require a Java 5 JVM to run
stuff we build. We currently restrict to 1.4 across the board.
Here's what I'm thinking:
- MRM and Continuum should switch now. Stuff built there is rarely
consumed elsewhere, and a Java 5 requirement outside of that is r
Or can't Maven offer you to upgrade like it does with plugin (or use to)?
On 7/5/06, Jesse McConnell <[EMAIL PROTECTED]> wrote:
yep, totally...its just that 3.7 should never be 'fuzzy' from a
dependency standpoint unless it is 3.7-SNAPSHOT or this new idea of
incrementing pom versions for same j
> -Original Message-
> From: Tomasz Pik [mailto:[EMAIL PROTECTED]
...
> So it seems that the roadmap will be:
> * Mylar project will provide 'Abstraction API' for and implementations for
> various trackers;
Yes, Mylar will provide this via it's Tasks API which has abstractions for
reposi
hello, there's a new site documentations for the war plugin in the
trunk. There's a better example of how to configure
webResources. it's the 4th draft, if you have any comments please
post it in MWAR-48.
Mike Perham wrote:
> Looks like Brett committed draft 2 of the doc update in MWAR-48
Hi,
How about we setup some lists for the repository manager?
Jason van Zyl
[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi all,
I have a maven2 ear project that depends on a maven2 ejb project. When I
used maven1, the ear plugin made sure the application.xml file was built
correctly, and everything was done for you.
This doesn't work with maven2, I get the following error:
18:08:13,632 WARN [EJBDeployer] Verify
I think PMD is in good shape. We've upgraded to PMD 3.7, added a bunch
of tests and upgraded the documentation. Can someone tell me how to run
the docck checker so I can verify the docs before publishing the site?
The RC snapshot binary is maven-pmd-plugin-2.1-20060706.192528-1.jar.
Roadmap wit
Wonder if that's not due to the pom.
related to that issue is the fact that the build of the
maven-jar-plugin site requires the changelog plugin which is only
available in the plugins/sandbox
Not very practical nor intuitive...
J
---
See in this case I'm not so much trying to invoke a plugin A from plugin
B but rather configure plugin A from plugin B. Though I somewhat agree
that this could lead to some really odd things occurring.
Besides generating the manifest myself, the only other possibility I can
think of is to basical
Looks like Brett committed draft 2 of the doc update in MWAR-48 and someone
published the site, bugs and all. So the war site documentation needs to be
polished and published ASAP. You can read through the patches attached to that
issue and see if they provide the info you need.
-Original
On 6 Jul 06, at 4:15 PM 6 Jul 06, Gary Paige wrote:
I am waiting for some fixes in the maven embedder and was wondering
if/when a 2.1 release of maven will happening.
No firm date yet but the design documents are here:
http://docs.codehaus.org/display/MAVEN/Maven+2.1+Design+Documents
The
On the documentation site for the WAR plugin
(http://maven.apache.org/plugins/maven-war-plugin/), the "Filtering war
dependencies" link is broken. Which is unfortunate, because that's exactly the
information I need right now. :P
--Matthew Beermann
I am waiting for some fixes in the maven embedder and was wondering
if/when a 2.1 release of maven will happening.
Thanks for the time.
Gary
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL P
Hi!
I'm trying to set up a project with several modules using the maven idea
plugin.
It seems as if the default module type is just an empty string, causing IDEA
not
to recognize them.
Changing the following line in module.jelly:
to
Seems to fix the problem.
I'm using maven v1.0.2 and int
Thanks :) Ignore my mail
Kenney Westerhof wrote:
On Thu, 6 Jul 2006, Geoffrey De Smet wrote:
Hi Geoffrey,
This issue is already fixed:
http://jira.codehaus.org/browse/MNG-2282
-- Kenney
I looked in JIRA, but couldn't find this bug.
But I am not sure in which module it should belong, I pres
On Thu, 6 Jul 2006, Geoffrey De Smet wrote:
Hi Geoffrey,
This issue is already fixed:
http://jira.codehaus.org/browse/MNG-2282
-- Kenney
> I looked in JIRA, but couldn't find this bug.
> But I am not sure in which module it should belong, I presume "wagon"?
> If it's a not already reported bug
I think it's already filed under MNG, back in the times the codehaus
repo was down and caused the same error.
On 7/6/06, Geoffrey De Smet <[EMAIL PROTECTED]> wrote:
I looked in JIRA, but couldn't find this bug.
But I am not sure in which module it should belong, I presume "wagon"?
If it's a not
I looked in JIRA, but couldn't find this bug.
But I am not sure in which module it should belong, I presume "wagon"?
If it's a not already reported bug, say so and I 'll file it in JIRA.
Basically I have 2 repo's:
- repo.domain.com (an internal one which is currently spitting out 502's
error co
On Thu, 6 Jul 2006, Rinku wrote:
Hi,
> Hi ,
>
> I am not sure about 'updating' plugin configuration from another one;
> but to obtain a reference to JAR plugin, you could try something like
> below (from the maven-eclipse-plugin sources):
The code below was a bit of a hack of mine to get access
Hi,
I've got a problem.
I'm using org.codehaus.plexus.util.cli.Commandline to execute java, but to
do it i need to add tools.jar as a argument. How to access this jar using
dependency from my pom.xml??
Pozdrawiam
Sebastian Błoch
- - - - - - - - - - - - - - - - - - - - - - - - - - - -
Configura
Modified: maven/repository-manager/trunk/maven-repository-webapp/pom.xml
URL:
http://svn.apache.org/viewvc/maven/repository-manager/trunk/maven-repository-webapp/pom.xml?rev=419521&r1=419520&r2=419521&view=diff
==
---
Using mvn 2.0.4
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] The projects in the reactor contain a cyclic reference: Edge
between 'Vertex{label='org.apac
jerome lacoste wrote:
On 7/5/06, Steve Loughran <[EMAIL PROTECTED]> wrote:
Ralph Goers wrote:
>
>
> Carlos Sanchez wrote:
>>
>> Yes you can, it's not the best way to do it but you can, by adding
>> explicitly the dependency with the versoin you want to your pom. In
>> the very worst case you hav
On 7/5/06, Steve Loughran <[EMAIL PROTECTED]> wrote:
Jochen Wiedmann wrote:
> On 7/4/06, Steve Loughran <[EMAIL PROTECTED]> wrote:
>
>> That'll be the ant-that-has-to-support-java-1.2 on
>> everything-and-build-with-no-dependencies, won't it?
>
> Be that as it may, but personally I prefer this ov
On 7/4/06, Mik Kersten <[EMAIL PROTECTED]> wrote:
Thanks for pulling me in Jason, this is good timing. In terms of Mylar's
'Connectors' we currently have a robust and well tested framework for
querying Bugzilla and JIRA. Trac will be ready for experimentation within a
week or so, and no, there
44 matches
Mail list logo
