Hi Nicolas,
Thanks for your work.
Could you file it in JIRA?
http://jira.codehaus.org/browse/MEV
Cheers,
Vincent
> -Original Message-
> From: Nicolas De Loof [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, October 19, 2005 8:24 AM
> To: Maven Developers List
> Subject: [co
create a MEV issue and attach your file.
Emmanuel
Nicolas De Loof a écrit :
Here is my 2 cents contrib to maven 2 : poms for sun javax.xml APIs +
javamail 1.3.3
http://loof.free.fr/javax-poms.zip
Nico.
This message contains information that may be privileged or confidential
and is the p
Here is my 2 cents contrib to maven 2 : poms for sun javax.xml APIs +
javamail 1.3.3
http://loof.free.fr/javax-poms.zip
Nico.
This message contains information that may be privileged or confidential and is
the property of the Capgemini Group. It is intended only for the person to whom
it
)
http://maven.apache.org/reference/standard-sun-jar-names.html
> Upload Sun POMs for non redistributable jars
>
>
> Key: MEV-8
> URL: http://jira.codehaus.org/browse/MEV-8
> Project: Maven Evangelism
> Type
Carlos Sanchez wrote:
I meant deploying to m2 repo so everything in the m1 gets autogenerated.
- sync'ed repos should go to a temp folder and converted to m2 repo
- each upload bundle should be converted to m2 and deployed in the m2
repo, and not i the m1 one
then all the m2 repo would be conv
I meant deploying to m2 repo so everything in the m1 gets autogenerated.
- sync'ed repos should go to a temp folder and converted to m2 repo
- each upload bundle should be converted to m2 and deployed in the m2
repo, and not i the m1 one
then all the m2 repo would be converted to m1.
This has se
Carlos Sanchez wrote:
At some point we definitely want to make changes to maven2 repo and
automatically generate the maven1 as there's much more information in
m2 poms wich can't be captured in m1 poms.
For achieving that we need:
- tool to convert m2 repo to m1
at the moment we are doing it
implementations
clearly visible in the groupId/artifactId. I don't know but there may be
additional non-freely available implementations from IBM and/or BEA.
> Upload Sun POMs for non redistributable jars
>
>
> Key: MEV-8
>
lines for
groupId naming.
> Upload Sun POMs for non redistributable jars
>
>
> Key: MEV-8
> URL: http://jira.codehaus.org/browse/MEV-8
> Project: Maven Evangelism
> Type: Task
> Report
having one group for each api which
will be a pain.
Anyway for m2 it shouldn't matter as they will be under javax.whatever (package
name), am I right ?
> Upload Sun POMs for non redistributable jars
>
>
> Key: MEV-8
>
[ http://jira.codehaus.org/browse/MEV-8?page=comments#action_39766 ]
Brett Porter commented on MEV-8:
I have done:
activation
javamail
jdo
jca
jdbc-stdext
jta
> Upload Sun POMs for non redistributable j
At some point we definitely want to make changes to maven2 repo and
automatically generate the maven1 as there's much more information in
m2 poms wich can't be captured in m1 poms.
For achieving that we need:
- tool to convert m2 repo to m1
- tool to convert m1 upload requests poms to m2 poms, so
Just for info,
where did you put those POMs in maven1/maven2 repo ?
Nico.
> I think so - what do you think?
>
> Carlos Sanchez wrote:
>
> >So from now on should I update the maven2 repo directly?
> >
> >On 5/25/05, Brett Porter <[EMAIL PROTECTED]> wrote:
> >
> >
> >>I just put them in m2.
I think so - what do you think?
Carlos Sanchez wrote:
So from now on should I update the maven2 repo directly?
On 5/25/05, Brett Porter <[EMAIL PROTECTED]> wrote:
I just put them in m2. I didn't put them in the m1 repo as it was not
possible to specify all the elements needed and they woul
>
> - Brett
>
> Carlos Sanchez wrote:
>
> >Hi,
> >
> >While uploading Sun POMs (MEV-8) I have noticed that some of them are
> >already in the maven2 repo but not in the maven1 one. As I was told to
> >upload poms to maven1 repo and avoid touching the mave
I just put them in m2. I didn't put them in the m1 repo as it was not
possible to specify all the elements needed and they wouldn't be used
from there.
- Brett
Carlos Sanchez wrote:
Hi,
While uploading Sun POMs (MEV-8) I have noticed that some of them are
already in the maven
Hi,
While uploading Sun POMs (MEV-8) I have noticed that some of them are
already in the maven2 repo but not in the maven1 one. As I was told to
upload poms to maven1 repo and avoid touching the maven2 I'd like to
know if they should be removed from maven2 and added to maven1 or the
instruc
[ http://jira.codehaus.org/browse/MEV-8?page=comments#action_39661 ]
Carlos Sanchez commented on MEV-8:
--
Yes, some are already, we just need to "evangelize" about them and add the
package tag.
> Upload Sun POMs for non redistr
from tomcat and it is
already there.
> Upload Sun POMs for non redistributable jars
>
>
> Key: MEV-8
> URL: http://jira.codehaus.org/browse/MEV-8
> Project: Maven Evangelism
> Type: Task
>
[ http://jira.codehaus.org/browse/MEV-8?page=all ]
Carlos Sanchez updated MEV-8:
-
Description:
activation
ejb-3.0
jaxrpc
jsp api
servlet api
jms
javamail
was:
Summary: Upload Sun POMs for non redistributable jars (was: Upload Sun
POMs or non
Upload Sun POMs or non redistributable jars
---
Key: MEV-8
URL: http://jira.codehaus.org/browse/MEV-8
Project: Maven Evangelism
Type: Task
Reporter: Carlos Sanchez
Assigned to: Carlos Sanchez
--
This message is
21 matches
Mail list logo
