[ http://jira.codehaus.org/browse/CONTINUUM-422?page=comments#action_50168
]
Emmanuel Venisse commented on CONTINUUM-422:
! is the right icon when a build fail. Or I don't understand what you mean
States is ! when build fails.
In the delete project page mention the project's name
-
Key: CONTINUUM-423
URL: http://jira.codehaus.org/browse/CONTINUUM-423
Project: Continuum
Type: Improvement
Components: continuum-web
Versions: 1.0
Do not add again the same project
-
Key: CONTINUUM-424
URL: http://jira.codehaus.org/browse/CONTINUUM-424
Project: Continuum
Type: Bug
Components: continuum-web
Versions: 1.0
Reporter: Vincent Massol
I added some
Explain that uploading a POM file works only for a single project without
modules
-
Key: CONTINUUM-425
URL: http://jira.codehaus.org/browse/CONTINUUM-425
Project: Continuum
Type:
[ http://jira.codehaus.org/browse/CONTINUUM-423?page=all ]
Emmanuel Venisse closed CONTINUUM-423:
--
Assign To: Emmanuel Venisse
Resolution: Fixed
Fix Version: 1.0.1
Already fixed.
In the delete project page mention the project's
[ http://jira.codehaus.org/browse/CONTINUUM-422?page=comments#action_50172
]
Fritz Oconer commented on CONTINUUM-422:
From the previous versions the State of the project is set to X when build
fails.
States is ! when build fails.
[ http://jira.codehaus.org/browse/CONTINUUM-422?page=all ]
Emmanuel Venisse closed CONTINUUM-422:
--
Resolution: Won't Fix
it was an error in the previous version.
! is used when a project build failed
x is used when we have an error like a scm
Distribution:
http://maven.zones.apache.org/~continuum/builds/continuum-20051107.133000.tar.gz
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051107.133000.txt
cannot add project using url with authentication (https)
Key: CONTINUUM-426
URL: http://jira.codehaus.org/browse/CONTINUUM-426
Project: Continuum
Type: Bug
Components: continuum-web
Versions: 1.0
[ http://jira.codehaus.org/browse/CONTINUUM-426?page=comments#action_50206
]
Dan Allen commented on CONTINUUM-426:
-
The sample url provided above should be an https url since that is my
specific test case. I cannot confirm if this happens with non-SSL
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051107.153000.txt
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051107.18.txt
[ http://jira.codehaus.org/browse/CONTINUUM-421?page=all ]
Emmanuel Venisse closed CONTINUUM-421:
--
Franck' tests run successfully.
Jabber notifier doens't support a domain name different of host name
Distribution:
http://maven.zones.apache.org/~continuum/builds/continuum-20051107.213001.tar.gz
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051107.213001.txt
Distribution:
http://maven.zones.apache.org/~continuum/builds/continuum-20051108.00.tar.gz
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051108.00.txt
create an XML report of all the failures in all the builds
--
Key: CONTINUUM-427
URL: http://jira.codehaus.org/browse/CONTINUUM-427
Project: Continuum
Type: New Feature
Components: continuum-web
[ http://jira.codehaus.org/browse/CONTINUUM-44?page=comments#action_50285 ]
james strachan commented on CONTINUUM-44:
-
I'd include in this OS as well. We want to test all our code in CI using
various OSes and JDK versions - then we'd really like to
[ http://jira.codehaus.org/browse/MAVENUPLOAD-569?page=all ]
Carlos Sanchez closed MAVENUPLOAD-569:
--
Assign To: Carlos Sanchez
Resolution: Fixed
Copied everything by hand
You may want to move the plugin to maven-plugins.sf.net, we'll
[ http://jira.codehaus.org/browse/MAVENUPLOAD-580?page=all ]
Carlos Sanchez closed MAVENUPLOAD-580:
--
Assign To: Carlos Sanchez
Resolution: Fixed
Upload wsdl4j 1.5.1
---
Key: MAVENUPLOAD-580
URL:
[ http://jira.codehaus.org/browse/MAVENUPLOAD-581?page=all ]
Carlos Sanchez closed MAVENUPLOAD-581:
--
Assign To: Carlos Sanchez
Resolution: Fixed
Upload wicket-1.1-bundle.jar and wicket-extensions-1.1-bundle.jar
[ http://jira.codehaus.org/browse/MAVENUPLOAD-533?page=all ]
Carlos Sanchez closed MAVENUPLOAD-533:
--
Assign To: Carlos Sanchez
Resolution: Incomplete
Upload XOM 1.1b4 to maven
-
Key: MAVENUPLOAD-533
[ http://jira.codehaus.org/browse/MAVENUPLOAD-530?page=all ]
Carlos Sanchez closed MAVENUPLOAD-530:
--
Assign To: Carlos Sanchez
Resolution: Incomplete
JCommon RC1 upload
--
Key: MAVENUPLOAD-530
URL:
[ http://jira.codehaus.org/browse/MEV-179?page=all ]
Carlos Sanchez closed MEV-179:
--
Assign To: Carlos Sanchez
Resolution: Won't Fix
Axis 1.2.1 WSDL4J dependency points to wrong place
--
[
http://jira.codehaus.org/browse/MAVENUPLOAD-578?page=comments#action_50226 ]
Brian Bonner commented on MAVENUPLOAD-578:
--
Code is open sourced by IBM. What is the groupid based upon? It's hosted on
sourceforge project, but all packages on code
[ http://jira.codehaus.org/browse/MEV-186?page=all ]
Carlos Sanchez closed MEV-186:
--
Assign To: Carlos Sanchez
Resolution: Won't Fix
displaytag has wrong dependency for jstl
Key: MEV-186
[ http://jira.codehaus.org/browse/MEV-186?page=comments#action_50227 ]
Carlos Sanchez commented on MEV-186:
But there's a relocation pom, this should'n be needed at all and we don't want
to start changing all the poms when another is moved from place
[ http://jira.codehaus.org/browse/MEV-186?page=comments#action_50228 ]
Oliver Siegmar commented on MEV-186:
I don't know what a relocation pom is, but in one of my projects jstl 1.0.2 and
1.1.2 get both included, because one is from groupId
[ http://jira.codehaus.org/browse/MEV-187?page=comments#action_50229 ]
Carlos Sanchez commented on MEV-187:
we can fix the pom.currentVersion, but what can we do with the other versions?
this needs to be reported to activemq guys
ActiveMQ 3.2 POM is
[
http://jira.codehaus.org/browse/MAVENUPLOAD-578?page=comments#action_50230 ]
Carlos Sanchez commented on MAVENUPLOAD-578:
http://maven.apache.org/guides/mini/guide-ibiblio-upload.html
it has to follow the package name rules, what means that
[ http://jira.codehaus.org/browse/MEV-186?page=comments#action_50231 ]
Carlos Sanchez commented on MEV-186:
Read MEV-177
displaytag has wrong dependency for jstl
Key: MEV-186
URL:
[ http://jira.codehaus.org/browse/MEV-187?page=comments#action_50232 ]
Jeff Genender commented on MEV-187:
---
Based on this being in ibiblio and you are the gate keepers (per Brett) this
should never have gotten into ibiblio in the first place. IMHO, you
[ http://jira.codehaus.org/browse/MEV-187?page=comments#action_50233 ]
Jeff Genender commented on MEV-187:
---
Whoops...that link i gave for our personal repo is on codehaus.
ActiveMQ 3.2 POM is invalid (contains variable refs based on maven 1)
[
http://jira.codehaus.org/browse/MAVENUPLOAD-578?page=comments#action_50236 ]
Brian Bonner commented on MAVENUPLOAD-578:
--
I'm asking Jeff Lee (on the project team) what his thought are. Since it's
open sourced, I'm going to guess they go for
Errors occurred while performing maven-1 to maven-2 repository conversion.
For more details, see:
http://test.maven.codehaus.org/reports/repoclean/07-Nov-2005_04.30.40/repository.report.txt
-
To unsubscribe, e-mail: [EMAIL
Hi,
On 11/7/05, Brett Porter (JIRA) [EMAIL PROTECTED] wrote:
we won't be allowing maven-model-2.0-all into the plugin, its v4 classes will
conflict with the root classloader.
What is needed is a way to get maven-model-3.0.1 into the plugin, really.
That may be best done by changing the
[
http://jira.codehaus.org/browse/MAVENUPLOAD-578?page=comments#action_50240 ]
Carlos Sanchez commented on MAVENUPLOAD-578:
If they wanna go with com.ibm.as400 then a web page at ibm.com saying that the
project is hosted there and called as400
Fixed.
I also removed the extra surefire directory in that repository as it
was inconsistent with all the others. So you can check it out with:
svn co https://svn.apache.org/repos/asf/maven/surefire/trunk surefire
- Brett
Emmanuel Venisse wrote:
Thanks Jason.
Jason van Zyl a écrit :
Hi,
[ http://jira.codehaus.org/browse/MNG-1449?page=all ]
Brett Porter closed MNG-1449:
-
Assign To: Brett Porter
Resolution: Won't Fix
that's not a bug. It's valid to have a jar with no sources (eg, just resources).
IT does print a warning
Maven
[ http://jira.codehaus.org/browse/MNG-699?page=comments#action_50245 ]
Brett Porter commented on MNG-699:
--
it's up to you. If you think the mojo versions are better, take those - or
combine the two.
I just think the final destination should be the Apache
best practices: deployment of aggregate JARs produced by the assembly plug-in
-
Key: MNG-1452
URL: http://jira.codehaus.org/browse/MNG-1452
Project: Maven 2
Type: Task
Components: best
[ http://jira.codehaus.org/browse/MNG-1452?page=comments#action_50247 ]
Brett Porter commented on MNG-1452:
---
if this is done with a classifier or just a change in extension, then it would
complicate the system to create a new POM.
Is anything in the POM
[ http://jira.codehaus.org/browse/MNG-1310?page=comments#action_50248 ]
Jerome Lacoste commented on MNG-1310:
-
MNG-1251 was checked in, but my patch not taken in. In particular, the
overloaded attachArtifact() method has not been made visible from the
Hi,
I suggest you to create two repos (snapshots and releases) under the
cargo project. When the sync program is available it's just a matter
of rsync the releases repo to ibiblio. In the meantime you can add it
to the pom and be able to build. Just remember to use fully qualified
groupIds
[ http://jira.codehaus.org/browse/MNG-1247?page=comments#action_50249 ]
Julien Dubois commented on MNG-1247:
Even if it's the Manifest parser's fault, this should at least be documented
clearly in the POM documentation.
I've got the same problem on Mac
Thanks.
On 11/5/05, Phil Steitz [EMAIL PROTECTED] wrote:
Carlos Sanchez wrote:
Hi,
Some days ago I created a patch to fix a lot of commons poms. If
somebody with enough karma could try to push this through...
http://issues.apache.org/bugzilla/show_bug.cgi?id=37314
Will do in next
[ http://jira.codehaus.org/browse/CONTINUUM-367?page=all ]
Emmanuel Venisse closed CONTINUUM-367:
--
Resolution: Fixed
Fixed. We certainly need to do more work on continuum-xml-rpc, but this issue
is fixed.
error when calling getprojects()
[ http://jira.codehaus.org/browse/CONTINUUM-378?page=comments#action_50251
]
Scott Schram commented on CONTINUUM-378:
They are all set to the default group and DEFAULT_SCHEDULE.
I did change them, experimenting with the program, then changed them
saaj pom wrong?
---
Key: MRM-24
URL: http://jira.codehaus.org/browse/MRM-24
Project: Maven Repository Manager
Type: Bug
Reporter: Robert Egglestone
Priority: Minor
The saaj pom contains the details for jaxm rather than saaj:
[ http://jira.codehaus.org/browse/CONTINUUM-378?page=comments#action_50252
]
Emmanuel Venisse commented on CONTINUUM-378:
I'll check if schedule deleted in database are stopped too. If it's the pb, you
need to resynchronize schedules and
Relocate tonic and jarjar groupIds to com.tonicsystems
--
Key: MEV-188
URL: http://jira.codehaus.org/browse/MEV-188
Project: Maven Evangelism
Type: Improvement
Reporter: Carlos Sanchez
Assigned to: Edwin
[ http://jira.codehaus.org/browse/MEV-189?page=all ]
Carlos Sanchez moved MRM-24 to MEV-189:
---
Priority: (was: Minor)
Key: MEV-189 (was: MRM-24)
Project: Maven Evangelism (was: Maven Repository Manager)
saaj pom wrong?
Distribution:
http://maven.zones.apache.org/~maven/builds/m2-20051108.001500.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051108.001500.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
[ http://jira.codehaus.org/browse/MEV-169?page=all ]
Edwin Punzalan closed MEV-169:
--
Resolution: Fixed
I see them now... Yesterday when I looked, its not there yet.
I'm closing this issue now.
Relocated dependency for tagsoup in xom
[ http://jira.codehaus.org/browse/MEV-177?page=comments#action_50254 ]
Edwin Punzalan commented on MEV-177:
Something must have gone wrong during the update of 1.0.2... In our copies in
SVN, 1.0.2 has the relocation.
Maybe Carlos can shed some light
Errors occurred while performing maven-1 to maven-2 repository conversion.
For more details, see:
http://test.maven.codehaus.org/reports/repoclean/07-Nov-2005_08.30.33/repository.report.txt
-
To unsubscribe, e-mail: [EMAIL
[ http://jira.codehaus.org/browse/MNG-1356?page=comments#action_50255 ]
John Casey commented on MNG-1356:
-
are these containers artifacts that could be resolved as part of a
plugin-dependency? That is to say, could you do:
build
plugins
plugin
[ http://jira.codehaus.org/browse/MNG-1356?page=comments#action_50256 ]
John Casey commented on MNG-1356:
-
Alternately, if your plugin is downloading the containers, can't you simply use
a plugin configuration that specifies ${java.io.tmp.dir} as the value?
[ http://jira.codehaus.org/browse/MNG-1388?page=comments#action_50257 ]
John Casey commented on MNG-1388:
-
This happens because dependency POMs aren't currently candidates for profile
triggering.
However, it seems we will have to trigger profiles for these
[ http://jira.codehaus.org/browse/MNG-1379?page=comments#action_50258 ]
John Casey commented on MNG-1379:
-
is this a problem with the eclipse plugin??
Wrong path for artifacts with system scope
--
Key:
[ http://jira.codehaus.org/browse/MNG-1379?page=comments#action_50260 ]
John Casey commented on MNG-1379:
-
I just tested this with a (somewhat) out-of-date 2.0-beta-3-SNAPSHOT build of
the maven-eclipse-plugin, and from what I could tell of the .classpath
[ http://jira.codehaus.org/browse/MNG-1130?page=all ]
Brett Porter reopened MNG-1130:
---
forgot to apply jar-sign-verify.diff. needs to be updated to apply.
Support jar signing.
Key: MNG-1130
URL:
[ http://jira.codehaus.org/browse/MNG-997?page=comments#action_50262 ]
John Casey commented on MNG-997:
Brett,
What's this about? Is it pending still?
create modules for other projects in the reactor
[ http://jira.codehaus.org/browse/MNG-997?page=all ]
Brett Porter closed MNG-997:
Assign To: Brett Porter
Resolution: Duplicate
Fix Version: (was: 2.0.1)
mng-998 actually implemented this.
998 was meant to be for when the module was
Exception error messages and i18n
-
Key: MNG-1453
URL: http://jira.codehaus.org/browse/MNG-1453
Project: Maven 2
Type: Improvement
Components: maven-core
Versions: 2.0
Environment: all
Reporter: Corridor Software
[ http://jira.codehaus.org/browse/MNG-1323?page=comments#action_50268 ]
John Casey commented on MNG-1323:
-
It looks like some of the work I did to get the ant-mojo support up and running
was related to this. Kenney's 04/Nov/2005 post was related to my fix
[ http://jira.codehaus.org/browse/MNG-1104?page=comments#action_50269 ]
John Casey commented on MNG-1104:
-
is this so you don't have to commit when you've just changed a dependency
version away from a -SNAPSHOT?
release plugin should ignore pom.xml from
[ http://jira.codehaus.org/browse/MNG-1104?page=comments#action_50271 ]
John Casey commented on MNG-1104:
-
I suppose the next step is always to commit the pom.xml with the new version/
before tagging, so it's not that big of a deal...
release plugin
[ http://jira.codehaus.org/browse/MEV-177?page=comments#action_50272 ]
Tomislav Stojcevich commented on MEV-177:
-
It seems to be ok now. The old version must have been cached somewhere or the
mirrors had sync issue or something.
older jstl jars
[ http://jira.codehaus.org/browse/MEV-177?page=all ]
Tomislav Stojcevich closed MEV-177:
---
Resolution: Fixed
older jstl jars in old location need relocation tag added
-
Key:
[ http://jira.codehaus.org/browse/MEV-188?page=all ]
Carlos Sanchez closed MEV-188:
--
Resolution: Fixed
Relocate tonic and jarjar groupIds to com.tonicsystems
--
Key: MEV-188
Errors occurred while performing maven-1 to maven-2 repository conversion.
For more details, see:
http://test.maven.codehaus.org/reports/repoclean/08-Nov-2005_12.30.21/repository.report.txt
-
To unsubscribe, e-mail: [EMAIL
[ http://jira.codehaus.org/browse/MEV-189?page=all ]
Edwin Punzalan closed MEV-189:
--
Resolution: Fixed
Fixed
saaj pom wrong?
---
Key: MEV-189
URL: http://jira.codehaus.org/browse/MEV-189
Project: Maven
[ http://jira.codehaus.org/browse/MNG-1452?page=comments#action_50275 ]
Jason van Zyl commented on MNG-1452:
We are going to have to do some legwork at the front-end or at the back-end. I
think making a POM that actually represents what's in the JAR is
[ http://jira.codehaus.org/browse/MNG-1356?page=comments#action_50276 ]
Vincent Massol commented on MNG-1356:
-
Hi John,
Yes, it's Cargo which is downloading the container distribution.
Using a plugin configuration is exactly what I'm after but it
[ http://jira.codehaus.org/browse/MEV-183?page=all ]
Edwin Punzalan closed MEV-183:
--
Assign To: Edwin Punzalan
Resolution: Fixed
Move common-test to its correct directory
-
Key: MEV-183
[ http://jira.codehaus.org/browse/MNG-1394?page=all ]
Edwin Punzalan updated MNG-1394:
Attachment: MNG-1394-maven-project.patch
Please see attached patch.
Use of the RelativePath Multi-Module produces failure
[ http://jira.codehaus.org/browse/MNG-1430?page=comments#action_50279 ]
Dietrich Schulten commented on MNG-1430:
Not sure. Can we assume that everybody wants the wtp builders and natures for
war? There are other web application plugins. Besides we
[ http://jira.codehaus.org/browse/MNG-1355?page=comments#action_50280 ]
Edwin Punzalan commented on MNG-1355:
-
Hi, the cause of the infinite loop is not the depth of the project and/or the
modules in it.
Look in the ui-toolkit/subproject/swing/pom.xml
[ http://jira.codehaus.org/browse/MAVENUPLOAD-580?page=all ]
Joerg Schaible reopened MAVENUPLOAD-580:
Hi Carlos, you forgot the second bundle. I remember, that I saw a comment of
you to add additional bundles in the same JIRA issue instead of
[ http://jira.codehaus.org/browse/MNG-1104?page=all ]
John Tolentino updated MNG-1104:
Attachment: MNG-1104-maven-release-plugin.patch
Added filter in getStatus() method.
release plugin should ignore pom.xml from status check
wsdl4j-qname
Key: MAVENUPLOAD-582
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-582
Project: maven-upload-requests
Type: Sub-task
Reporter: Joerg Schaible
Found the create sub-task functionality now ... :)
--
This message is automatically
[ http://jira.codehaus.org/browse/MEV-169?page=comments#action_50169 ]
Yann Le Du commented on MEV-169:
Seems to be OK the way it is (as far as I'm concerned...)
http://www.ibiblio.org/maven2/org/ccil/cowan/tagsoup/tagsoup/0.9.7/ is complete
Sounds good to me and, as you said, users won't probably know which
component(s) is(are) affected anyway.
Cheers,
Stéphane
On 11/7/05, Brett Porter [EMAIL PROTECTED] wrote:
Hi,
I was wondering what folks though of changing maven-artifact,
maven-core, etc in JIRA to be user friendly
[ http://jira.codehaus.org/browse/CONTINUUM-413?page=all ]
Emmanuel Venisse closed CONTINUUM-413:
--
Resolution: Fixed
I updated FAQ with Brian informations.
We'll provide later a maven.bat file for users
build reported as successful on win
Hi,
Some POMs in central repo are using ${pom.groupId} and ${pom.currentVersion},
e.g.
http://www.ibiblio.org/maven2/directory-shared/apache-ldapber-provider/0.9/apache-ldapber-provider-0.9.pom
I'm ready to file MEV issues for some of these, but before I do so, I just want
to be sure that they
NPE thrown when parsing bad plugin jar
--
Key: MNG-1445
URL: http://jira.codehaus.org/browse/MNG-1445
Project: Maven 2
Type: Bug
Versions: 2.0
Environment: Java 1.5.0 on Linux
Reporter: Bob Allison
Due to a
[ http://jira.codehaus.org/browse/MNG-1445?page=all ]
Bob Allison updated MNG-1445:
-
Attachment: MNG-1445-testcase.zip
The attached test case contains two projects:
-- testplugin creates a simple plugin
-- test references the plugin
To replicate the
${pom.groupId} will convert correctly.
${pom.currentVersion} s be translated in the repository converter to
${pom.version} but is not currently. You could certainly file patches
for these.
- Brett
Yann Le Du wrote:
Hi,
Some POMs in central repo are using ${pom.groupId} and
unable to config goals that are not bound to part of the standard lifecycle
---
Key: MNG-1446
URL: http://jira.codehaus.org/browse/MNG-1446
Project: Maven 2
Type: Bug
Versions: 2.0
[ http://jira.codehaus.org/browse/MNG-699?page=comments#action_50196 ]
Stephane Nicoll commented on MNG-699:
-
What do we do? Do we take MOJO-98 / MOJO-99 or the plugins I have added in the
sandbox?
We also need to add the ejb3 and par lifecycles to
Proxy
-
Key: MNG-1447
URL: http://jira.codehaus.org/browse/MNG-1447
Project: Maven 2
Type: Bug
Components: documentation - faqs
Versions: 2.0
Environment: Any
Reporter: Tarun Ramakrishna Elankath
It *should* be mentioned that Maven 2 uses the
Replace ${pom.currentVersion} with ${pom.version} in apacheds-main
--
Key: MEV-180
URL: http://jira.codehaus.org/browse/MEV-180
Project: Maven Evangelism
Type: Bug
Components: Dependencies
[ http://jira.codehaus.org/browse/MEV-181?page=comments#action_50197 ]
Yann Le Du commented on MEV-181:
My bad, title should be Replace ${pom.currentVersion} with ${pom.version} in
asn1-ber
Replace ${pom.currentVersion} with ${pom.version} in
Replace ${pom.currentVersion} with ${pom.version} in apacheds-main
--
Key: MEV-181
URL: http://jira.codehaus.org/browse/MEV-181
Project: Maven Evangelism
Type: Bug
Components: Dependencies
Replace ${pom.currentVersion} with ${pom.version} in apache-ldapber-provider
Key: MEV-182
URL: http://jira.codehaus.org/browse/MEV-182
Project: Maven Evangelism
Type: Bug
Reporter: Yann
[ http://jira.codehaus.org/browse/CONTINUUM-425?page=all ]
Emmanuel Venisse closed CONTINUUM-425:
--
Assign To: Emmanuel Venisse
Resolution: Fixed
Fix Version: 1.0.1
Done.
Explain that uploading a POM file works only for a single
Move common-test to its correct directory
-
Key: MEV-183
URL: http://jira.codehaus.org/browse/MEV-183
Project: Maven Evangelism
Type: Bug
Reporter: Yann Le Du
commons-test : commons-test : 0.1 is currently stored
emma 2.0.latest : how do we handle this ?
-
Key: MEV-184
URL: http://jira.codehaus.org/browse/MEV-184
Project: Maven Evangelism
Type: Bug
Reporter: Yann Le Du
Versions of emma:emma are in the form 2.0.build
[ http://jira.codehaus.org/browse/MEV-177?page=all ]
Tomislav Stojcevich reopened MEV-177:
-
It looks like all of them got updated except for the 1.0.2 version It's
timestamp changed like all the rest but the change is not in it. That's the
one
Easy way to tell if the plugin is for m2 or m1
--
Key: MNG-1448
URL: http://jira.codehaus.org/browse/MNG-1448
Project: Maven 2
Type: Bug
Components: maven-plugins
Reporter: Alexandre Poitras
--
This message is
1 - 100 of 128 matches
Mail list logo
