Re: upload POMs for non-free artifacts

2006-12-14 Thread Mark Hobson

On 14/12/06, nicolas de loof <[EMAIL PROTECTED]> wrote:

I've created MAVENUPLOAD-1273 for Oracle driver POMs.


Cheers for that, I was just looking these drivers myself.  I've added
10.2.0.2.0 versions to a new bundle on that issue.

Mark

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: upload POMs for non-free artifacts

2006-12-14 Thread nicolas de loof

I've created MAVENUPLOAD-1273 for Oracle driver POMs.

2006/12/14, nicolas de loof <[EMAIL PROTECTED]>:


I also would like those POMs to be maintained by vendors.. but they don't
seem to see interest for this. Look at Java api POMS : those restricted
artifacts have been include in maven public repo with naming conventions
with no support from SUN. The dev.java.net repo is a recent contrib of sun
to maven repository.

My goal is to have a "standard" groupId for those restricted artifacts, so
that you can find them using maven repo search engines, and not "reinvent
the wheel" if your project needs the orcale JDBC driver : my corporate
Maven1 repo has 5 version of same driver, using various group/artifact !

I also agree about more section for artifacts. Any suggestion is welcome

2006/12/14, Craig McClanahan <[EMAIL PROTECTED]>:
>
> On 12/14/06, nicolas de loof <[EMAIL PROTECTED] > wrote:
> >
> > Hello,
> >
> > I've deployed some restricted libs to my corporate repository. Those
> libs
> > are for example Oracle JDBC driver or IBM MQSeries java client.
> > Can I make an upload request for such POMs in maven public repo ?
> > My goal is to avoid the "Sun jars hell" I got on maven1, where
> projects
> > made
> > reference to the same artifact with various groupId.
>
>
> What good is it to publish such poms in the public Maven repositories,
> if
> you cannot post the actual jar files they refer to?  And, it seems
> unlikely
> to me that you have the legal right to publish all of the jars
> referenced in
> your follow-up list.
>
> The right solution is to encourage the vendors of the stuff you need to
> publish their own software, with the group and artifact ids that *they*
> choose.  Trying to publish someone else's work, under an identifier that
> *you* choose, strikes me as an attempt at plagarism.
>
> Craig
>
> Nico.
> >
> >
>
>



Re: upload POMs for non-free artifacts

2006-12-14 Thread nicolas de loof

I also would like those POMs to be maintained by vendors.. but they don't
seem to see interest for this. Look at Java api POMS : those restricted
artifacts have been include in maven public repo with naming conventions
with no support from SUN. The dev.java.net repo is a recent contrib of sun
to maven repository.

My goal is to have a "standard" groupId for those restricted artifacts, so
that you can find them using maven repo search engines, and not "reinvent
the wheel" if your project needs the orcale JDBC driver : my corporate
Maven1 repo has 5 version of same driver, using various group/artifact !

I also agree about more section for artifacts. Any suggestion is welcome

2006/12/14, Craig McClanahan <[EMAIL PROTECTED]>:


On 12/14/06, nicolas de loof <[EMAIL PROTECTED]> wrote:
>
> Hello,
>
> I've deployed some restricted libs to my corporate repository. Those
libs
> are for example Oracle JDBC driver or IBM MQSeries java client.
> Can I make an upload request for such POMs in maven public repo ?
> My goal is to avoid the "Sun jars hell" I got on maven1, where projects
> made
> reference to the same artifact with various groupId.


What good is it to publish such poms in the public Maven repositories, if
you cannot post the actual jar files they refer to?  And, it seems
unlikely
to me that you have the legal right to publish all of the jars referenced
in
your follow-up list.

The right solution is to encourage the vendors of the stuff you need to
publish their own software, with the group and artifact ids that *they*
choose.  Trying to publish someone else's work, under an identifier that
*you* choose, strikes me as an attempt at plagarism.

Craig

Nico.
>
>




Re: upload POMs for non-free artifacts

2006-12-14 Thread Carlos Sanchez

On 12/14/06, Craig McClanahan <[EMAIL PROTECTED]> wrote:

On 12/14/06, nicolas de loof <[EMAIL PROTECTED]> wrote:
>
> Hello,
>
> I've deployed some restricted libs to my corporate repository. Those libs
> are for example Oracle JDBC driver or IBM MQSeries java client.
> Can I make an upload request for such POMs in maven public repo ?
> My goal is to avoid the "Sun jars hell" I got on maven1, where projects
> made
> reference to the same artifact with various groupId.


What good is it to publish such poms in the public Maven repositories, if
you cannot post the actual jar files they refer to?  And, it seems unlikely
to me that you have the legal right to publish all of the jars referenced in
your follow-up list.


Standarization, you may need to install by hand the jar, but everybody
can use the same groupId and artifactId. The point is try to avoid the
chaos that happened before with Sun jars when people using 5+ names to
refer to the same thing.

We are not going to publish the jars, I didn't get what do you mean
about legal rights.



The right solution is to encourage the vendors of the stuff you need to
publish their own software, with the group and artifact ids that *they*
choose.  Trying to publish someone else's work, under an identifier that
*you* choose, strikes me as an attempt at plagarism.


that'd be great, if there's any chance that they'll do that I will
hold and let them propose. We do that with Sun people given that they
are already involved.

I don't think we should publish poms for all commercial software in
the world, but if maven users request them and are willing to provide
poms with information and dependencies, we shouldn't stop them either



Craig

Nico.
>
>





--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: upload POMs for non-free artifacts

2006-12-14 Thread Craig McClanahan

On 12/14/06, nicolas de loof <[EMAIL PROTECTED]> wrote:


Hello,

I've deployed some restricted libs to my corporate repository. Those libs
are for example Oracle JDBC driver or IBM MQSeries java client.
Can I make an upload request for such POMs in maven public repo ?
My goal is to avoid the "Sun jars hell" I got on maven1, where projects
made
reference to the same artifact with various groupId.



What good is it to publish such poms in the public Maven repositories, if
you cannot post the actual jar files they refer to?  And, it seems unlikely
to me that you have the legal right to publish all of the jars referenced in
your follow-up list.

The right solution is to encourage the vendors of the stuff you need to
publish their own software, with the group and artifact ids that *they*
choose.  Trying to publish someone else's work, under an identifier that
*you* choose, strikes me as an attempt at plagarism.

Craig

Nico.





Re: upload POMs for non-free artifacts

2006-12-14 Thread Carlos Sanchez

- do you also know the dependencies between them?
- you'd need to use three or more sections in groupIds (from package
names if possible). It's very unlikely that ibm only produce the mq
jars ;)

On 12/14/06, nicolas de loof <[EMAIL PROTECTED]> wrote:

Here is my (suggested) POM list :

Oracle JDBC driver :
groupId : com.oracle
artifactId : classes12
version : 9.0.2.0.0 (according to MANIFEST)

groupId : com.oracle
artifactId : classes12
version : 8.1.7

groupId : com.oracle
artifactId : ojdbc14
version : 9.0.2.0.0 (according to MANIFEST)

IBM MQ Series (Websphere MQ) :

groupId : com.ibm
artifactId : mq
version : 5.3.04

groupId : com.ibm
artifactId : mqbind
version : 5.3.04

groupId : com.ibm
artifactId : mqjms
version : 5.3.04

IBM jsse implementation :

groupId : com.ibm
artifactId : ibmjsse
version : 1.0.2

BEA Jolt

groupId : com.bea
artifactId : jolt
version : 8.0

groupId : com.bea
artifactId : joltasp
version : 8.0

groupId : com.bea
artifactId : joltatm
version : 8.0

groupId : com.bea
artifactId : joltjse
version : 8.0

groupId : com.bea
artifactId : joltwls
version : 8.0

groupId : com.bea
artifactId : jolti18n
version : 8.0

groupId : com.bea
artifactId : joltadmin
version : 8.0

JNDI wrapper (used by watij)

groupId : com.jniwrapper
artifactId : comfyj
version : 2.2

groupId : com.jniwrapper
artifactId : jexplorer
version : 1.7

groupId : com.jniwrapper
artifactId : jniwrap
version : 3.4

groupId : com.jniwrapper
artifactId : mshtml
version : 1.6

groupId : com.jniwrapper
artifactId : winpack
version : 3.5

SUN jndi providers :

groupId : com.sun.jndi
artifactId : fscontext
version : 1.2

groupId : com.sun.jndi
artifactId : ldap
version : 1.2.4

groupId : com.sun.jndi
artifactId : ldapbp
version : 1.2.4

groupId : com.sun.jndi
artifactId : ldpasec
version : 1.2.4

groupId : com.sun.jndi
artifactId : nis
version : 1.2.1

groupId : com.sun.jndi
artifactId : providerutils
version : 1.2.4

groupId : com.sun.jndi
artifactId : rmiregistry
version : 1.2

groupId : com.sun.jndi
artifactId : dsml
version : 1.2

groupId : com.sun.jndi
artifactId : dns
version : 1.2

groupId : com.sun.jndi
artifactId : cosnaming
version : 1.2.1


Unigone ASN1 :

groupId : com.unigone
artifactId : asn1RT
version : 2.0.4

groupId : com.unigone
artifactId : asn1Compiler
version : 2.0.4

groupId : com.unigone
artifactId : unigoneCommon
version : 2.0.4

Ilog JRULES :

groupId : com.ilog
artifactId : diagramall
version : 4.6.5 / 5.1.3.25

groupId : com.ilog
artifactId : sam
version : 1.0.0.1

groupId : com.ilog
artifactId : wuidhtml
version : 4.6.5 / 5.1.3.25

groupId : com.ilog.views
artifactId : appframe
version : 4.6.5 / 5.5

groupId : com.ilog.views
artifactId : graphlayout
version : 5.5

groupId : com.ilog.views
artifactId : jviews
version : 5.5

groupId : com.ilog.views
artifactId : jviews-framework-dhtml
version : 6.0

groupId : com.ilog.views
artifactId : jviews-web-components
version : 6.0

groupId : com.ilog.views
artifactId : jviewssvg
version : 5.5

groupId : com.ilog.views
artifactId : prototypes
version : 5.5

groupId : com.ilog.views
artifactId : sdm
version : 5.5

groupId : com.ilog.jrules
artifactId : jrules-all
version : 4.6.4.38

groupId : com.ilog.jrules
artifactId : jrules-bal40
version : 5.1.3.25

groupId : com.ilog.jrules
artifactId : jrules-beans
version : 4.6.4.38 / 5.1.3.25

groupId : com.ilog.jrules
artifactId : jrules-binding
version : 4.6.4.38

groupId : com.ilog.jrules
artifactId : jrules-bres-builder
version : 5.1.3.25

groupId : com.ilog.jrules
artifactId : jrules-bres-execution
version : 5.1.3.25

groupId : com.ilog.jrules
artifactId : jrules-bres-manage-tools
version : 5.1.3.25

groupId : com.ilog.jrules
artifactId : jrules-bres-rep-tasks
version : 5.1.3.25

groupId : com.ilog.jrules
artifactId : jrules-bres-session-java
version : 5.1.3.25

groupId : com.ilog.jrules
artifactId : jrules-bres-setup
version : 5.1.3.25

groupId : com.ilog.jrules
artifactId : jrules-bres-tools
version : 5.1.3.25

groupId : com.ilog.jrules
artifactId : jrules-builder
version : 5.1.3.25

groupId : com.ilog.jrules
artifactId : jrules-consistency
version : 4.6.4.38 / 5.1.5.35

groupId : com.ilog.jrules
artifactId : jrules-engine
version : 4.6.4.38 / 5.1.3.25

groupId : com.ilog.jrules
artifactId : jrules-jsr94
version : 5.1.3.25


Re: upload POMs for non-free artifacts

2006-12-14 Thread nicolas de loof

Here is my (suggested) POM list :

Oracle JDBC driver :
   groupId : com.oracle
   artifactId : classes12
   version : 9.0.2.0.0 (according to MANIFEST)

   groupId : com.oracle
   artifactId : classes12
   version : 8.1.7

   groupId : com.oracle
   artifactId : ojdbc14
   version : 9.0.2.0.0 (according to MANIFEST)

IBM MQ Series (Websphere MQ) :

   groupId : com.ibm
   artifactId : mq
   version : 5.3.04

   groupId : com.ibm
   artifactId : mqbind
   version : 5.3.04

   groupId : com.ibm
   artifactId : mqjms
   version : 5.3.04

IBM jsse implementation :

   groupId : com.ibm
   artifactId : ibmjsse
   version : 1.0.2

BEA Jolt

   groupId : com.bea
   artifactId : jolt
   version : 8.0

   groupId : com.bea
   artifactId : joltasp
   version : 8.0

   groupId : com.bea
   artifactId : joltatm
   version : 8.0

   groupId : com.bea
   artifactId : joltjse
   version : 8.0

   groupId : com.bea
   artifactId : joltwls
   version : 8.0

   groupId : com.bea
   artifactId : jolti18n
   version : 8.0

   groupId : com.bea
   artifactId : joltadmin
   version : 8.0

JNDI wrapper (used by watij)

   groupId : com.jniwrapper
   artifactId : comfyj
   version : 2.2

   groupId : com.jniwrapper
   artifactId : jexplorer
   version : 1.7

   groupId : com.jniwrapper
   artifactId : jniwrap
   version : 3.4

   groupId : com.jniwrapper
   artifactId : mshtml
   version : 1.6

   groupId : com.jniwrapper
   artifactId : winpack
   version : 3.5

SUN jndi providers :

   groupId : com.sun.jndi
   artifactId : fscontext
   version : 1.2

   groupId : com.sun.jndi
   artifactId : ldap
   version : 1.2.4

   groupId : com.sun.jndi
   artifactId : ldapbp
   version : 1.2.4

   groupId : com.sun.jndi
   artifactId : ldpasec
   version : 1.2.4

   groupId : com.sun.jndi
   artifactId : nis
   version : 1.2.1

   groupId : com.sun.jndi
   artifactId : providerutils
   version : 1.2.4

   groupId : com.sun.jndi
   artifactId : rmiregistry
   version : 1.2

   groupId : com.sun.jndi
   artifactId : dsml
   version : 1.2

   groupId : com.sun.jndi
   artifactId : dns
   version : 1.2

   groupId : com.sun.jndi
   artifactId : cosnaming
   version : 1.2.1


Unigone ASN1 :

   groupId : com.unigone
   artifactId : asn1RT
   version : 2.0.4

   groupId : com.unigone
   artifactId : asn1Compiler
   version : 2.0.4

   groupId : com.unigone
   artifactId : unigoneCommon
   version : 2.0.4

Ilog JRULES :

   groupId : com.ilog
   artifactId : diagramall
   version : 4.6.5 / 5.1.3.25

   groupId : com.ilog
   artifactId : sam
   version : 1.0.0.1

   groupId : com.ilog
   artifactId : wuidhtml
   version : 4.6.5 / 5.1.3.25

   groupId : com.ilog.views
   artifactId : appframe
   version : 4.6.5 / 5.5

   groupId : com.ilog.views
   artifactId : graphlayout
   version : 5.5

   groupId : com.ilog.views
   artifactId : jviews
   version : 5.5

   groupId : com.ilog.views
   artifactId : jviews-framework-dhtml
   version : 6.0

   groupId : com.ilog.views
   artifactId : jviews-web-components
   version : 6.0

   groupId : com.ilog.views
   artifactId : jviewssvg
   version : 5.5

   groupId : com.ilog.views
   artifactId : prototypes
   version : 5.5

   groupId : com.ilog.views
   artifactId : sdm
   version : 5.5

   groupId : com.ilog.jrules
   artifactId : jrules-all
   version : 4.6.4.38

   groupId : com.ilog.jrules
   artifactId : jrules-bal40
   version : 5.1.3.25

   groupId : com.ilog.jrules
   artifactId : jrules-beans
   version : 4.6.4.38 / 5.1.3.25

   groupId : com.ilog.jrules
   artifactId : jrules-binding
   version : 4.6.4.38

   groupId : com.ilog.jrules
   artifactId : jrules-bres-builder
   version : 5.1.3.25

   groupId : com.ilog.jrules
   artifactId : jrules-bres-execution
   version : 5.1.3.25

   groupId : com.ilog.jrules
   artifactId : jrules-bres-manage-tools
   version : 5.1.3.25

   groupId : com.ilog.jrules
   artifactId : jrules-bres-rep-tasks
   version : 5.1.3.25

   groupId : com.ilog.jrules
   artifactId : jrules-bres-session-java
   version : 5.1.3.25

   groupId : com.ilog.jrules
   artifactId : jrules-bres-setup
   version : 5.1.3.25

   groupId : com.ilog.jrules
   artifactId : jrules-bres-tools
   version : 5.1.3.25

   groupId : com.ilog.jrules
   artifactId : jrules-builder
   version : 5.1.3.25

   groupId : com.ilog.jrules
   artifactId : jrules-consistency
   version : 4.6.4.38 / 5.1.5.35

   groupId : com.ilog.jrules
   artifactId : jrules-engine
   version : 4.6.4.38 / 5.1.3.25

   groupId : com.ilog.jrules
   artifactId : jrules-jsr94
   version : 5.1.3.25

   groupId : com.ilog.jrules
   artifactId : jrules-repository
   version : 4.6.4.38 / 5.1.3.25

   groupId : com.ilog.jrules
   artifactId : jrules-rulesservice
   version : 5.1.5.35

   groupId : com.ilog.jrules
   artifactId : jrules-serverj2ee
   version : 5.1.5.35

   groupId : com.ilog.jrules
   artifactId : jrules-webui
   version : 4.6.4.38 / 5.1.3.25

   groupId : com.ilog.jrules
   artifactId : logging
   version : 4.

Re: upload POMs for non-free artifacts

2006-12-14 Thread Carlos Sanchez

yes, if you make a list of groupIds / artifactIds for review then you
can just provide a zip with the poms for upload.
Also it's very interesting adding the sha1 md5 of the jars so people
can check if the jar they have matches the pom.

On 12/14/06, nicolas de loof <[EMAIL PROTECTED]> wrote:

Hello,

I've deployed some restricted libs to my corporate repository. Those libs
are for example Oracle JDBC driver or IBM MQSeries java client.
Can I make an upload request for such POMs in maven public repo ?
My goal is to avoid the "Sun jars hell" I got on maven1, where projects made
reference to the same artifact with various groupId.

Nico.





--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



upload POMs for non-free artifacts

2006-12-14 Thread nicolas de loof

Hello,

I've deployed some restricted libs to my corporate repository. Those libs
are for example Oracle JDBC driver or IBM MQSeries java client.
Can I make an upload request for such POMs in maven public repo ?
My goal is to avoid the "Sun jars hell" I got on maven1, where projects made
reference to the same artifact with various groupId.

Nico.