>
> Regards,
>
> Hervé
>
> [1] https://issues.apache.org/jira/browse/MNG-6571
>
> [2] https://github.com/apache/maven/tree/MNG-6571
>
> Le mercredi 23 janvier 2019, 10:10:40 CET Dameron, Yann a écrit :
> > Hi,
> >
> >
> >
> > I
;t detect such cases and duplicate everything.
Is Maven optimized to detect such cases? It would be great to ensure that
Dependency (and others) instances are not duplicated.
Thanks,
Yann
Information in this e-mail and any attachments is confidential, and may not be
copied or used by anyone other
This problem concerns issue MNG-3586 (which is planned for alpha-3)
It doesn't concern only WSGEN plugin but all plugins that use tools.jar
dependency with system scope
Henri Gomez a écrit :
It's not in the iteration for alpha-2 either, but if you want to try and
tackle this we can add it to t
doesn't exist.
I have also tried to play with the MavenArchiver component but without
succes.
Can someone help me on how to get the Manifest configuration of a M2
project ?
Thank you for your help
Yann.
-
To unsubscri
it is the right list and the right time to react....
Yann.
Jesse McConnell wrote:
+1
On 1/11/07, Fabrizio Giustina <[EMAIL PROTECTED]> wrote:
+1
fabrizio
On 1/8/07, Stephane Nicoll <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I'd like to release the ear plugin which contains a
It exists an issue for the war plugin (MWAR-9) that seems to depend on
PLX-158.
As we are stuck with those issues could someone help on this?
Do you know if it could be solve with maven 2.0.5?
FYI there are 34 votes for issue MWAR-9
Thanks
Yann
+1 for all (non-binding)
IMHO, taglist report could as well be moved, though less essential.
- Yann
On 3/10/06, Brett Porter < [EMAIL PROTECTED]> wrote:
>
> A month ago I sent a proposal for discussion, to bring some mojos into
> the Maven plugins project, because
> a) orig
[ http://jira.codehaus.org/browse/MEV-355?page=all ]
Yann Le Du updated MEV-355:
---
Attachment: jboss-common-4.0.2.pom
> Missing deps in jboss-common 4.0.2
> --
>
> Key: MEV-355
> URL: http://ji
rter: Yann Le Du
Since svn://svn.codehaus.org/maven/scm/repository/ is not up-to-date yet, I
cannot make a diff. The patch is to add the following in both jbossmq-client &
jnp-client POMs :
{code:xml}
jboss
jboss-common
4.0.2
{code}
--
This me
Missing deps in jboss-common 4.0.2
--
Key: MEV-355
URL: http://jira.codehaus.org/browse/MEV-355
Project: Maven Evangelism
Type: Bug
Components: Dependencies
Reporter: Yann Le Du
Index: jboss-common-4.0.2.pom
[
http://jira.codehaus.org/browse/MAVENUPLOAD-764?page=comments#action_60289 ]
Yann Le Du commented on MAVENUPLOAD-764:
Thanks Carlos for the graph. I've made the following corrections (the bundles
are up-to-date) :
MAVENUPLOAD-764 (this one
+1
- Yann
> 2006/3/1, Jason van Zyl <[EMAIL PROTECTED]>:
> > > Hi,
> > >
> > > I just wanted to close this up as I think it's a good idea and
> anything
> > > that let's people manage their mail better IMO is a good thing.
> > &g
Please upload jbossha 4.0.2
---
Key: MAVENUPLOAD-764
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-764
Project: maven-upload-requests
Type: Task
Reporter: Yann Le Du
This is JBoss High Availability and Clustering.
--
This message
[
http://jira.codehaus.org/browse/MAVENUPLOAD-763?page=comments#action_59838 ]
Yann Le Du commented on MAVENUPLOAD-763:
Erratum in description, this is jboss-j2ee 4.0.0 as stated in the bundle name
> Please upload jboss-j2ee 4.
Please upload jboss-j2ee 4.0.2
--
Key: MAVENUPLOAD-763
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-763
Project: maven-upload-requests
Type: Task
Reporter: Yann Le Du
This is JBoss J2EE Implementation.
--
This message is
Please upload jboss-client 4.0.2
Key: MAVENUPLOAD-762
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-762
Project: maven-upload-requests
Type: Task
Reporter: Yann Le Du
This is JBoss Application Server Client
JBoss
[ http://jira.codehaus.org/browse/MNG-2099?page=comments#action_59362 ]
Yann Le Du commented on MNG-2099:
-
I don't get the problem with doxia trunk - anchors are correct. Maybe it's
already corrected ??
Would it solve http://maven.apache.org/m
[ http://jira.codehaus.org/browse/MNG-2099?page=comments#action_59355 ]
Yann Le Du commented on MNG-2099:
-
I've noticed the same thing in FAQs, e.g. http://maven.apache.org/general.html
Am I wrong or is it a problem with FML ? There is no # for name in
[ http://jira.codehaus.org/browse/MNG-2103?page=all ]
Yann Le Du updated MNG-2103:
Attachment: test-inheritance-true.zip
> Inheritance of overrides that of
> -
>
> Key: MNG-2103
&g
[ http://jira.codehaus.org/browse/MNG-2103?page=comments#action_59235 ]
Yann Le Du commented on MNG-2103:
-
Hmm... In this case, I would understand the false as
"don't inherit whatever is in ". So, in modules, is not
inherited and both d
es and can be added there on request
I don't get this one :)
- Yann
What do you think of other solutions:
- subscribe to commits@ and filter out the actual commits
- subscribe to filters from JIRA (so you get a daily mail of all the
open or new issues in a particular project)
- use RSS fr
discussions. But SVN commits are way less important.
- Yann
Versions: 2.0.2
Reporter: Yann Le Du
Priority: Minor
Anchors in http://maven.apache.org/maven-model/maven.html should be (e.g.) :
instead of
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http
[
http://jira.codehaus.org/browse/MAVENUPLOAD-735?page=comments#action_58331 ]
Yann Le Du commented on MAVENUPLOAD-735:
1.0.4 is the reference implementation version of JWSDP 1.5 :
http://java.sun.com/webservices/docs/1.5/jaxb/ReleaseNotes.html
[
http://jira.codehaus.org/browse/MAVENUPLOAD-725?page=comments#action_58329 ]
Yann Le Du commented on MAVENUPLOAD-725:
displaytag-1.0 (the jar, that also contains the tld in META-INF) can be
downloaded at
http://sourceforge.net/project
Please upload jnp-client 4.0.2
--
Key: MAVENUPLOAD-738
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-738
Project: maven-upload-requests
Type: Task
Reporter: Yann Le Du
Part of JBoss application server 4.0.2
--
This message is
Please upload jbossmq-client 4.0.2
--
Key: MAVENUPLOAD-737
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-737
Project: maven-upload-requests
Type: Task
Reporter: Yann Le Du
Part of JBoss application server 4.0.2
--
This
Please upload com.sun.xml:xercesImpl 1.0.4
--
Key: MAVENUPLOAD-736
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-736
Project: maven-upload-requests
Type: Task
Reporter: Yann Le Du
Part of the Java Web Services
Please upload com.sun.xml:xalan 1.0.4
-
Key: MAVENUPLOAD-735
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-735
Project: maven-upload-requests
Type: Task
Reporter: Yann Le Du
Part of the Java Web Services Developer Pack
Please upload jaxb-xjc 1.0.4
Key: MAVENUPLOAD-734
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-734
Project: maven-upload-requests
Type: Task
Reporter: Yann Le Du
Part of the Java Web Services Developer Pack 1.5
Bundle contains
Please upload jaxb-libs 1.0.4
-
Key: MAVENUPLOAD-733
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-733
Project: maven-upload-requests
Type: Task
Reporter: Yann Le Du
Part of the Java Web Services Developer Pack 1.5
Bundle
Please upload jaxb-impl 1.0.4
-
Key: MAVENUPLOAD-732
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-732
Project: maven-upload-requests
Type: Task
Reporter: Yann Le Du
Part of the Java Web Services Developer Pack 1.5
Bundle
Description of jaxb-api 1.0.1 is wrong
--
Key: MEV-325
URL: http://jira.codehaus.org/browse/MEV-325
Project: Maven Evangelism
Type: Bug
Reporter: Yann Le Du
Index: jaxb-api-1.0.1.pom
Please upload displaytag 12 tld
---
Key: MAVENUPLOAD-725
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-725
Project: maven-upload-requests
Type: Task
Reporter: Yann Le Du
This is the tld distributed with displaytag 1.0 as
[ http://jira.codehaus.org/browse/CONTINUUM-256?page=comments#action_57130
]
Yann Le Du commented on CONTINUUM-256:
--
If it can help : I made a few tests on our server. We currently have about 70
M2 projects on Continuum.
Running the builds causes no
: Inheritence and Interpolation
Versions: 2.0.2
Environment: Maven 2.0.2
Continuum 1.0.2 with maven-scm-*-1.0-beta-3-20060115.041342-*.jar
Reporter: Yann Le Du
Quoting Emmanuel Venisse from user list :
Ok, it's a bug in
http://svn.apache.org/viewcvs.cgi/maven/components/trunk/maven-projec
[ http://jira.codehaus.org/browse/WAGON-30?page=comments#action_56747 ]
Yann Le Du commented on WAGON-30:
-
Maybe the trick would be to use -p :
-p, --parents no error if existing, make parent directories as needed
> wagon-file failed when used by ma
[ http://jira.codehaus.org/browse/WAGON-30?page=comments#action_56640 ]
Yann Le Du commented on WAGON-30:
-
Even with the patch, wagon-file fails for directories that don't already exist.
If you can, first create required directories then run deploy
-38
Project: Maven 2.x Plug-in for Eclipse
Type: Bug
Reporter: Yann Le Du
Assigned to: Eugene Kuleshov
Priority: Minor
According to MNGECLIPSE-37, update site has changed.
Please correct this in the Flash demo :
http://m2eclipse.codehaus.org
[ http://jira.codehaus.org/browse/MEV-282?page=comments#action_55423 ]
Yann Le Du commented on MEV-282:
Honestly, I don't know about this public draft version (only mere 2.0 is
available at Sun's now), but as there already was a 2.0.publi
Please relocate jspapi:jsp-api to javax.servlet:jsp-api
---
Key: MEV-282
URL: http://jira.codehaus.org/browse/MEV-282
Project: Maven Evangelism
Type: Improvement
Reporter: Yann Le Du
Since these versions are
(Oops, just noticed this was the dev list, sorry to bug.)
I don't understand, the maven-pmd-plugin has also that nice page, doesn't it
?
http://maven.apache.org/plugins/maven-pmd-plugin/
http://maven.apache.org/plugins/maven-pmd-plugin/pmd-mojo.html
--
Yann
2006/1/9, Mike Perh
Hi Mike,
Use the plugin-plugin :
~
~
~ ...
~
~maven-plugin-plugin
~
~ ...
--
Yann
2006/1/9, Mike Perham <[EMAIL PROTECTED]>:
>
> How do I generate the nice documentation page for each goal which lists
> the parameters that Mojo takes?
>
Gilles,
You could checkout sources :
svn co https://svn.apache.org/repos/asf/maven/components/trunkmaven-components
svn co https://svn.apache.org/repos/asf/maven/plugins/trunk maven-plugins
--
Yann
2006/1/9, Scokart Gilles <[EMAIL PROTECTED]>:
>
>
>
> I notice that there is no
[ http://jira.codehaus.org/browse/CONTINUUM-401?page=comments#action_54773
]
Yann Le Du commented on CONTINUUM-401:
--
Using these parameters in continuum/bin/linux/wrapper.conf solved the "out of
memory error" for us :
...
# Initial Java Hea
[ http://jira.codehaus.org/browse/MNG-1703?page=comments#action_54251 ]
Yann Le Du commented on MNG-1703:
-
Hi Edwin, sorry, I wanted to post yesterday, but JIRA was down.
You were right, is inherited. Yet, is not, hence my
test failure.
Should I close
[ http://jira.codehaus.org/browse/CONTINUUM-401?page=all ]
Yann Le Du updated CONTINUUM-401:
-
Attachment: wrapper-2005-12-21.log
> cannot delete project (stuck on 'in progress')
> --
commons-email contains wrong dependencies
-
Key: MEV-262
URL: http://jira.codehaus.org/browse/MEV-262
Project: Maven Evangelism
Type: Bug
Components: Dependencies
Reporter: Yann Le Du
javamail
[ http://jira.codehaus.org/browse/MNG-1703?page=comments#action_53561 ]
Yann Le Du commented on MNG-1703:
-
I tried with a brand new Maven 2.0.1 installation and got the same thing.
What I'm trying to do is to run an Ant script at process-resources
Reporter: Yann Le Du
springframework
spring
1.2-RC2
Please change version to 1.2-rc2 (uncapitalized)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure
[
http://jira.codehaus.org/browse/MAVENUPLOAD-637?page=comments#action_53532 ]
Yann Le Du commented on MAVENUPLOAD-637:
Filed in Struts : http://issues.apache.org/bugzilla/show_bug.cgi?id=37927
> Please upload Struts HTML Taglib 1.
Please upload Struts Tiles Taglib 1.2.4
---
Key: MAVENUPLOAD-640
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-640
Project: maven-upload-requests
Type: Task
Reporter: Yann Le Du
--
This message is automatically
Please upload Struts Nested Taglib 1.2.4
Key: MAVENUPLOAD-639
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-639
Project: maven-upload-requests
Type: Task
Reporter: Yann Le Du
--
This message is automatically
Please upload Struts Logic Taglib 1.2.4
---
Key: MAVENUPLOAD-638
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-638
Project: maven-upload-requests
Type: Task
Reporter: Yann Le Du
--
This message is automatically
Please upload Struts HTML Taglib 1.2.4
--
Key: MAVENUPLOAD-637
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-637
Project: maven-upload-requests
Type: Task
Reporter: Yann Le Du
--
This message is automatically
Please upload Struts Bean Taglib 1.2.4
--
Key: MAVENUPLOAD-636
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-636
Project: maven-upload-requests
Type: Task
Reporter: Yann Le Du
--
This message is automatically
-plugin
Versions: 2.0
Reporter: Yann Le Du
Priority: Minor
In release:prepare, it would be nice that all prompted information can also be
passed as parameters :
* tag name (already available, -Dtag)
* release version
* new development version
It would allow to call the
[ http://jira.codehaus.org/browse/MNG-1736?page=all ]
Yann Le Du updated MNG-1736:
Attachment: MNG-1736-maven-site-plugin.patch
Changed ouside to outside
Correction is harmless since outside is the default value
> list-style-position: ouside; in ma
list-style-position: ouside; in maven-base.css
--
Key: MNG-1736
URL: http://jira.codehaus.org/browse/MNG-1736
Project: Maven 2
Type: Bug
Components: maven-site-plugin
Versions: 2.0.1
Reporter: Yann Le Du
: Yann Le Du
Priority: Minor
Attachments: before.png
In the left column, if you put text with long words - such as project names -
text overflows (see before.png)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators
[ http://jira.codehaus.org/browse/MNG-1738?page=all ]
Yann Le Du updated MNG-1738:
Attachment: after.png
MNG-1738-maven-site-plugin.patch
In #leftColumn, added :
overflow: auto;
See after.png
> Long words in left column overfl
[ http://jira.codehaus.org/browse/MNG-1543?page=comments#action_52517 ]
Yann Le Du commented on MNG-1543:
-
My previous comment can be a bit confusing because I forgot to mention
something. In order to get full dependency information in the deployed POM, I
[ http://jira.codehaus.org/browse/MNG-1543?page=comments#action_52515 ]
Yann Le Du commented on MNG-1543:
-
Please see linked issue MNG-1715. My concern is also about the POM that is
deploy-ed *along* the JAR, that we'd like to be :
* effective-pom
[ http://jira.codehaus.org/browse/MNG-1543?page=comments#action_52408 ]
Yann Le Du commented on MNG-1543:
-
Edwin, do you mean that the patch will be : "Do not generate an
exported-pom.xml and use the original pom.xml instead " ?
> pom.xm
Absolute paths in exported-pom.xml
--
Key: MNG-1715
URL: http://jira.codehaus.org/browse/MNG-1715
Project: Maven 2
Type: Bug
Components: Plugins and Lifecycle
Versions: 2.0
Reporter: Yann Le Du
Priority: Minor
is not propagated to child POMs
--
Key: MNG-1703
URL: http://jira.codehaus.org/browse/MNG-1703
Project: Maven 2
Type: Bug
Components: POM
Versions: 2.0
Reporter: Yann Le Du
section in
[ http://jira.codehaus.org/browse/CONTINUUM-401?page=comments#action_51637
]
Yann Le Du commented on CONTINUUM-401:
--
Actually I fortunaltely kept the old 1.0.1 directory. There was no error or
exception in the log during the night.
Are the builds
[ http://jira.codehaus.org/browse/MNG-1253?page=comments#action_50974 ]
Yann Le Du commented on MNG-1253:
-
Just noticed a related issue that makes this one duplicate, I think :
http://jira.codehaus.org/browse/MNG-1100
> Plugin versions are populated in n
[ http://jira.codehaus.org/browse/MEV-183?page=comments#action_50293 ]
Yann Le Du commented on MEV-183:
The changes are not effective on ibiblio... Maybe the directories need a
"touch" or something ?
> Move common-test to its corr
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
directory
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
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
Reporter: Yann Le Du
Please replace ${pom.currentVersion} with ${pom.version} in dependencies :
asn1-codec
Thx
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For
[ 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
Reporter: Yann Le Du
Please replace ${pom.currentVersion} with ${pom.version} for dependencies :
apacheds-shared
apacheds-core
Thx
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure
they really need to be corrected this way...
So please confirm to me whether I can start filing in JIRA.
Thanks,
Yann
___
Appel audio GRATUIT partout dans le monde avec le nouveau
[ 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
[ http://jira.codehaus.org/browse/MEV-174?page=comments#action_50051 ]
Yann Le Du commented on MEV-174:
Oh, and BTW,
0.9-SNAPSHOT
should be changed to
0.9
> Wrong apacheds-main dependency groupId in acegi-security
Wrong apacheds-main dependency groupId in acegi-security POM
Key: MEV-174
URL: http://jira.codehaus.org/browse/MEV-174
Project: Maven Evangelism
Type: Bug
Components: Dependencies
Reporter: Yann Le
Relocated dependency for tagsoup in xom
---
Key: MEV-169
URL: http://jira.codehaus.org/browse/MEV-169
Project: Maven Evangelism
Type: Improvement
Components: Dependencies
Reporter: Yann Le Du
Important : must be done
[ http://jira.codehaus.org/browse/MEV-35?page=comments#action_49914 ]
Yann Le Du commented on MEV-35:
---
Filed an upload request for this one : MAVENUPLOAD-573
> XOM POM references tagsoup which is not in the r
Please upload tagsoup 0.9.7
---
Key: MAVENUPLOAD-573
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-573
Project: maven-upload-requests
Type: Task
Reporter: Yann Le Du
Here is also a bundle for the relocation POM in tagsoup:tagsoup
Incorrect dependency for icu4j in xom
-
Key: MEV-166
URL: http://jira.codehaus.org/browse/MEV-166
Project: Maven Evangelism
Type: Bug
Components: Dependencies
Reporter: Yann Le Du
Please change icu4j dependency to
[ http://jira.codehaus.org/browse/MEV-34?page=comments#action_49905 ]
Yann Le Du commented on MEV-34:
---
Great, but you put it on groupId icu, whereas the groupId referenced in xom is
icu4j
I'll file an issue to update xom (a quick search shows that icu
[ http://jira.codehaus.org/browse/MNG-1398?page=comments#action_49819 ]
Yann Le Du commented on MNG-1398:
-
See MNG-1249
> site report generates an 'empty' target/site/apido
: 2.0
Reporter: Yann Le Du
maven-release-plugin 2.0-beta-2
My project depends upon org.hibernate:hibernate:3.0.5
hibernate depends upon dom4j, but excludes a bunch of dom4j dependencies
m2 release:prepare on my project produces a tag release-pom.xml that contains
dependency upon dom4j, but
: Improvement
Versions: 1.5.1
Reporter: Yann Le Du
changes-maven-plugin 2.0-beta-1
Default xmlPath is
* in changes-report : ${basedir}/src/changes/changes.xml
* in announcement-generate : ${basedir}/src/main/changes.xml
It would be nice they be the same.
--
This message is
)
Environment: maven-release-plugin 2.0-beta-2
Reporter: Yann Le Du
Note : this is with maven-release-plugin 2.0-beta-2 (had problems with beta-3)
Last iteration POM (before release) :
maven-homemade-plugin
[...]
I omit the plugin version because I use pluginManagement in
)
Reporter: Yann Le Du
Priority: Minor
MNG-650 is happening again
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http
[ http://jira.codehaus.org/browse/MNG-678?page=comments#action_48842 ]
Yann Le Du commented on MNG-678:
I switched to 2.0-RC (thus jsch-0.1.23), and I'm encountering these failures
(90% of the time)... although I had no problem with 2.0-beta-3 :)
Versions: 2.0-beta-3
Reporter: Yann Le Du
/COMMON/trunk/maven-plugins/maven-deps-plugin/pom.xml :
scm:svn:svn://host:3691/COMMON/trunk/maven-plugins/maven-deps-plugin/
scm:svn:svn://host:3691/COMMON/trunk/maven-plugins/maven-deps-plugin/
http://host.corp.com/viewcvs
[ http://jira.codehaus.org/browse/MNG-916?page=comments#action_48219 ]
Yann Le Du commented on MNG-916:
Unless I'm mistaken, the issue is still there in beta-3, i.e. Maven still looks
for the RELEASE version of my home-made plugin in my corp. repos
Reporter: Yann Le Du
Priority: Trivial
When you execute
m2 install:install-file -DgroupId=jdbc -DartifactId=jdbc -Dversion=2.0
-Dpackaging=jar -Dfile=/home/maven/repository-manual/jdbc/jdbc/2.0/jdbc-2.0.jar
in a parent project, the reactor executes it again in every subproject.
Harmless, but
,
so avoiding using maven-antrun-plugin in the future.
Regards,
Yann
--- "Brett Porter (JIRA)" <[EMAIL PROTECTED]> a écrit :
> [ http://jira.codehaus.org/browse/MNG-897?page=comments#action_47333 ]
>
> Brett Porter commented on MNG-897:
> --
[ http://jira.codehaus.org/browse/MNG-897?page=comments#action_47331 ]
Yann Le Du commented on MNG-897:
Apart from avoiding writing a Maven plugin when you don't know how, I see two
reasons why you would want to call Ant scripts from Maven :
* You ha
[ http://jira.codehaus.org/browse/CONTINUUM-243?page=comments#action_47163
]
Yann Le Du commented on CONTINUUM-243:
--
The custom default goal could be the one defined in POM's , see
http://jira.codehaus.org/browse/MNG-1011
> Ability to m
itory
~
~
~ ...
~
~
~
~
~ central
~ http://repo.corp.com/maven/repository
~ always
~
~
~
~
Yann
--- Brett Porter <[EMAIL PROTECTED]> a écrit :
> That's ok - I must have missed it on the users list. How was this
> working for you in alpha-3?
>
Thank you Brett,
Sorry for having filed in JIRA, but I did so because :
* this scenario was working in alpha-3
* I couldn't get a clue on the user list
Using a root POM is OK for me.
Yann
--- "Brett Porter (JIRA)" <[EMAIL PROTECTED]> a écrit :
> [ http://jira
eta-1
Reporter: Yann Le Du
Priority: Critical
I have set a corp. repository, and want local users to use this repo to
download latest corp. artifacts.
Altering the local settings.xml with
~
~ central
~ http://repo.corp.com/maven/repository
~
allows downloading only releases, not snap
Remove border for company logo
--
Key: CONTINUUM-314
URL: http://jira.codehaus.org/browse/CONTINUUM-314
Project: Continuum
Type: Wish
Components: continuum-web
Versions: 1.0-alpha-4
Reporter: Yann Le Du
Priority: Minor
1 - 100 of 141 matches
Mail list logo
