You are viewing a plain text version of this content. The canonical link for it is here.
Posted to repository@apache.org by robert burrell donkin <rd...@apache.org> on 2004/03/06 22:50:25 UTC
adding jaxme jars
i have a jelly tag library that uses jaxme (the apache JAXB
implementation currently under incubation) that i'd like to commit into
jakarta-commons. AIUI the right way to make ASF jars available for use
in mavenized builds is to upload them into the apache repository.
is this correct and is there any documentation about the right way to
do this?
- robert
Re: adding jaxme jars
Posted by "Mark R. Diggory" <md...@latte.harvard.edu>.
I have to get back to Jason, he was getting me an Ibilio account today.
I'll clean it up.
-Mark
Ben Walding wrote:
> One side effect of changing groupIds around after they have been
> mirrored is that ibiblio's maven repo now has jaxme stuff slotted into
> both /jaxme and /apache-jaxme. Once someone has decided which way it
> should be, we'll need to remove the old cruft. Mark, I leave this chore
> in your hands!
>
> Cheers,
>
> Ben
>
> robert burrell donkin wrote:
>
>> i have a jelly tag library that uses jaxme (the apache JAXB
>> implementation currently under incubation) that i'd like to commit
>> into jakarta-commons. AIUI the right way to make ASF jars available
>> for use in mavenized builds is to upload them into the apache repository.
>>
>> is this correct and is there any documentation about the right way to
>> do this?
>>
>> - robert
>>
>>
>
--
Mark Diggory
Software Developer
Harvard MIT Data Center
http://www.hmdc.harvard.edu
Re: adding jaxme jars
Posted by Ben Walding <be...@walding.com>.
One side effect of changing groupIds around after they have been
mirrored is that ibiblio's maven repo now has jaxme stuff slotted into
both /jaxme and /apache-jaxme. Once someone has decided which way it
should be, we'll need to remove the old cruft. Mark, I leave this chore
in your hands!
Cheers,
Ben
robert burrell donkin wrote:
> i have a jelly tag library that uses jaxme (the apache JAXB
> implementation currently under incubation) that i'd like to commit
> into jakarta-commons. AIUI the right way to make ASF jars available
> for use in mavenized builds is to upload them into the apache repository.
>
> is this correct and is there any documentation about the right way to
> do this?
>
> - robert
>
>
Re: adding jaxme jars
Posted by "Mark R. Diggory" <md...@latte.harvard.edu>.
More likely the mirroring process is still being problematic. I'll grill
Jason for a few minutes and get things updated.
-Mark
robert burrell donkin wrote:
> hi mark
>
> i can see the jaxme jars on apache but not in the maven repository on
> ibiblio. is there anything else i need to do to push the content over
> there?
>
> (or have i just make some mistake in the upload...)
>
> - robert
>
> On 8 Mar 2004, at 22:20, Mark R. Diggory wrote:
>
>>
>>
>> robert burrell donkin wrote:
>>
>>> hi mark
>>> i've given it a go myself but i have a few questions and i'd
>>> appreciate it if you'd check my work so far.
>>> On 7 Mar 2004, at 16:18, Mark R. Diggory wrote:
>>>
>>>> You need to establish what your groups id will be. The current
>>>> naming trend for Apache "xml" projects has been a bit haphazard.
>>>>
>>>> xercies
>>>> xml-security
>>>> xml-resolver
>>>> xalan
>>>>
>>>> Some standardization here would be good. But that will not effect
>>>> maven.
>>>
>>> i've had a chat on IRC and gone for apache-jaxme
>>>
>>>> There is currently a problem with Maven publishing to a BSD system
>>>> and md5 signature generation, if you do not want to use maven to do
>>>> the publishing then these are the tasks you need to complete:
>>>>
>>>> 1.) The easiest way right now is for you to place the jars into
>>>>
>>>> java-repository/xml-jaxme/jars/...
>>>
>>> gone (but apache-jaxme rather than xml-jaxme)
>>>
>>>> 2.) Generate an md5 signature for each one in the same directory.
>>>> For instance as an examples
>>>>
>>>> "md5 xml-jaxme-1.0.jar > xml-jaxme-1.0.jar.md5" will produce:
>>>>
>>>> java-repository/xml-jaxme/jars/xml-jaxme-1.0.jar
>>>> java-repository/xml-jaxme/jars/xml-jaxme-1.0.jar.md5
>>>
>>> done
>>>
>>>> 3.) Generate the following symlinks the above files from
>>>>
>>>> java-repository/xml-jaxme/jars/xml-jaxme-SNAPSHOT.jar
>>>> java-repository/xml-jaxme/jars/xml-jaxme-SNAPSHOT.jar.md5
>>>
>>> done
>>>
>>>> 4.) and create a file
>>>>
>>>> java-repository/xml-jaxme/jars/xml-jaxme-snapshot-version with the
>>>> contents "1.0"
>>>
>>> these releases are versioned 0.2: should this file contain 0.2 (since
>>> it refers to the version of the jars) or 1.0 (since it's a mavenesque
>>> version number)
>>
>>
>> It would be wise, so yes, apache-jaxme-0.2.jar
>>
>>>> 5.) use the following "POM" in the
>>>>
>>>> java-repository/xml-jaxme/poms/project/pom
>>>> <project>
>>>> <pomVersion>3</pomVersion>
>>>> <id>xml-jaxme</id>
>>>> <name>xml-jaxme</name>
>>>> <currentVersion>1.0</currentVersion>
>>>> <organization>
>>>> <name>Apache Software Foundation</name>
>>>> <url>www.apache.org</url>
>>>> </organization>
>>>> <licenses>
>>>> <license>
>>>> <name>ASL 2.0</name>
>>>> <url>???????</url>
>>>> <comments>???????</comments>
>>>> </license>
>>>> </licenses>
>>>> </project>
>>>
>>> there are a number of jar in the release. i'd been working on the
>>> theory that each needs a separate artifact id. what should the
>>> contents of the file be in this case?
>>> - robert
>>
>>
>> Yes, it should look like:
>>
>> /java-repository/apache-jaxme/jars/<artifact>-<version>.jar
>>
>> /java-repository/apache-jaxme/poms/project/pom
>>
>> <project>
>> <pomVersion>3</pomVersion>
>> <groupId>apache-jaxme</groupId>
>> <name>Apache Jaxme</name>
>> <currentVersion>0.2</currentVersion>
>> <organization>
>> <name>Apache Software Foundation</name>
>> <url>www.apache.org</url>
>> </organization>
>> <licenses>
>> <license>
>> <name>ASL 2.0</name>
>> <url>http://www.apache.org/licenses/LICENSE-2.0</url>
>> </license>
>> </licenses>
>> </project>
>>
>> sound good, I'll take a look in the directory and verify all looks well.
>>
>> --
>> Mark Diggory
>> Software Developer
>> Harvard MIT Data Center
>> http://www.hmdc.harvard.edu
>>
>
--
Mark Diggory
Software Developer
Harvard MIT Data Center
http://www.hmdc.harvard.edu
Re: adding jaxme jars
Posted by "Mark R. Diggory" <md...@latte.harvard.edu>.
Robert, this process is finished in java repository
http://www.apache.org/dist/java-repository/jaxme/jars/
I didn't bother maintain the pom, as it is apparent that the other
projects are not using them. We should have this sync'ed shortly.
-Mark
Mark R. Diggory wrote:
> I've started this process
>
> http://www.apache.org/dist/java-repository/jaxme/jars/
>
> Mark R. Diggory wrote:
>
>> Robert, the jars are there, we should probably do a little renaming.
>> My fault for not looking yesterday.
>>
>> http://www.ibiblio.org/maven/apache-jaxme/jars/
>> !!!!!!!!!!
>> http://www.ibiblio.org/maven/apache-jaxme/jars/jaxme-incubation-0.2.jar
>>
>> we should probably have it more simply be
>>
>> http://www.ibiblio.org/maven/jaxme/jars/jaxme-0.2.jar
>> http://www.ibiblio.org/maven/jaxme/jars/jaxme-SNAPSHOT.jar
>>
>> http://www.ibiblio.org/maven/jaxme/jars/jaxme-rt-0.2.jar
>> http://www.ibiblio.org/maven/jaxme/jars/jaxme-rt-SNAPSHOT.jar
>>
>> http://www.ibiblio.org/maven/jaxme/jars/jaxme-api-0.2.jar
>> http://www.ibiblio.org/maven/jaxme/jars/jaxme-api-SNAPSHOT.jar
>>
>> http://www.ibiblio.org/maven/jaxme/jars/jaxme-js-0.2.jar
>> http://www.ibiblio.org/maven/jaxme/jars/jaxme-js-SNAPSHOT.jar
>>
>> http://www.ibiblio.org/maven/jaxme/jars/jaxme-pm-0.2.jar
>> http://www.ibiblio.org/maven/jaxme/jars/jaxme-pm-SNAPSHOT.jar
>>
>> http://www.ibiblio.org/maven/jaxme/jars/jaxme-xs-0.2.jar
>> http://www.ibiblio.org/maven/jaxme/jars/jaxme-xs-SNAPSHOT.jar
>>
>> -Mark
>>
>> robert burrell donkin wrote:
>>
>>> hi mark
>>>
>>> i can see the jaxme jars on apache but not in the maven repository on
>>> ibiblio. is there anything else i need to do to push the content over
>>> there?
>>>
>>> (or have i just make some mistake in the upload...)
>>>
>>> - robert
>>>
>>> On 8 Mar 2004, at 22:20, Mark R. Diggory wrote:
>>>
>>>>
>>>>
>>>> robert burrell donkin wrote:
>>>>
>>>>> hi mark
>>>>> i've given it a go myself but i have a few questions and i'd
>>>>> appreciate it if you'd check my work so far.
>>>>> On 7 Mar 2004, at 16:18, Mark R. Diggory wrote:
>>>>>
>>>>>> You need to establish what your groups id will be. The current
>>>>>> naming trend for Apache "xml" projects has been a bit haphazard.
>>>>>>
>>>>>> xercies
>>>>>> xml-security
>>>>>> xml-resolver
>>>>>> xalan
>>>>>>
>>>>>> Some standardization here would be good. But that will not effect
>>>>>> maven.
>>>>>
>>>>>
>>>>>
>>>>> i've had a chat on IRC and gone for apache-jaxme
>>>>>
>>>>>> There is currently a problem with Maven publishing to a BSD system
>>>>>> and md5 signature generation, if you do not want to use maven to
>>>>>> do the publishing then these are the tasks you need to complete:
>>>>>>
>>>>>> 1.) The easiest way right now is for you to place the jars into
>>>>>>
>>>>>> java-repository/xml-jaxme/jars/...
>>>>>
>>>>>
>>>>>
>>>>> gone (but apache-jaxme rather than xml-jaxme)
>>>>>
>>>>>> 2.) Generate an md5 signature for each one in the same directory.
>>>>>> For instance as an examples
>>>>>>
>>>>>> "md5 xml-jaxme-1.0.jar > xml-jaxme-1.0.jar.md5" will produce:
>>>>>>
>>>>>> java-repository/xml-jaxme/jars/xml-jaxme-1.0.jar
>>>>>> java-repository/xml-jaxme/jars/xml-jaxme-1.0.jar.md5
>>>>>
>>>>>
>>>>>
>>>>> done
>>>>>
>>>>>> 3.) Generate the following symlinks the above files from
>>>>>>
>>>>>> java-repository/xml-jaxme/jars/xml-jaxme-SNAPSHOT.jar
>>>>>> java-repository/xml-jaxme/jars/xml-jaxme-SNAPSHOT.jar.md5
>>>>>
>>>>>
>>>>>
>>>>> done
>>>>>
>>>>>> 4.) and create a file
>>>>>>
>>>>>> java-repository/xml-jaxme/jars/xml-jaxme-snapshot-version with the
>>>>>> contents "1.0"
>>>>>
>>>>>
>>>>>
>>>>> these releases are versioned 0.2: should this file contain 0.2
>>>>> (since it refers to the version of the jars) or 1.0 (since it's a
>>>>> mavenesque version number)
>>>>
>>>>
>>>>
>>>>
>>>> It would be wise, so yes, apache-jaxme-0.2.jar
>>>>
>>>>>> 5.) use the following "POM" in the
>>>>>>
>>>>>> java-repository/xml-jaxme/poms/project/pom
>>>>>> <project>
>>>>>> <pomVersion>3</pomVersion>
>>>>>> <id>xml-jaxme</id>
>>>>>> <name>xml-jaxme</name>
>>>>>> <currentVersion>1.0</currentVersion>
>>>>>> <organization>
>>>>>> <name>Apache Software Foundation</name>
>>>>>> <url>www.apache.org</url>
>>>>>> </organization>
>>>>>> <licenses>
>>>>>> <license>
>>>>>> <name>ASL 2.0</name>
>>>>>> <url>???????</url>
>>>>>> <comments>???????</comments>
>>>>>> </license>
>>>>>> </licenses>
>>>>>> </project>
>>>>>
>>>>>
>>>>>
>>>>> there are a number of jar in the release. i'd been working on the
>>>>> theory that each needs a separate artifact id. what should the
>>>>> contents of the file be in this case?
>>>>> - robert
>>>>
>>>>
>>>>
>>>>
>>>> Yes, it should look like:
>>>>
>>>> /java-repository/apache-jaxme/jars/<artifact>-<version>.jar
>>>>
>>>> /java-repository/apache-jaxme/poms/project/pom
>>>>
>>>> <project>
>>>> <pomVersion>3</pomVersion>
>>>> <groupId>apache-jaxme</groupId>
>>>> <name>Apache Jaxme</name>
>>>> <currentVersion>0.2</currentVersion>
>>>> <organization>
>>>> <name>Apache Software Foundation</name>
>>>> <url>www.apache.org</url>
>>>> </organization>
>>>> <licenses>
>>>> <license>
>>>> <name>ASL 2.0</name>
>>>> <url>http://www.apache.org/licenses/LICENSE-2.0</url>
>>>> </license>
>>>> </licenses>
>>>> </project>
>>>>
>>>> sound good, I'll take a look in the directory and verify all looks
>>>> well.
>>>>
>>>> --
>>>> Mark Diggory
>>>> Software Developer
>>>> Harvard MIT Data Center
>>>> http://www.hmdc.harvard.edu
>>>>
>>>
>>
>
--
Mark Diggory
Software Developer
Harvard MIT Data Center
http://www.hmdc.harvard.edu
Re: adding jaxme jars
Posted by "Mark R. Diggory" <md...@latte.harvard.edu>.
I've started this process
http://www.apache.org/dist/java-repository/jaxme/jars/
Mark R. Diggory wrote:
> Robert, the jars are there, we should probably do a little renaming. My
> fault for not looking yesterday.
>
> http://www.ibiblio.org/maven/apache-jaxme/jars/
> !!!!!!!!!!
> http://www.ibiblio.org/maven/apache-jaxme/jars/jaxme-incubation-0.2.jar
>
> we should probably have it more simply be
>
> http://www.ibiblio.org/maven/jaxme/jars/jaxme-0.2.jar
> http://www.ibiblio.org/maven/jaxme/jars/jaxme-SNAPSHOT.jar
>
> http://www.ibiblio.org/maven/jaxme/jars/jaxme-rt-0.2.jar
> http://www.ibiblio.org/maven/jaxme/jars/jaxme-rt-SNAPSHOT.jar
>
> http://www.ibiblio.org/maven/jaxme/jars/jaxme-api-0.2.jar
> http://www.ibiblio.org/maven/jaxme/jars/jaxme-api-SNAPSHOT.jar
>
> http://www.ibiblio.org/maven/jaxme/jars/jaxme-js-0.2.jar
> http://www.ibiblio.org/maven/jaxme/jars/jaxme-js-SNAPSHOT.jar
>
> http://www.ibiblio.org/maven/jaxme/jars/jaxme-pm-0.2.jar
> http://www.ibiblio.org/maven/jaxme/jars/jaxme-pm-SNAPSHOT.jar
>
> http://www.ibiblio.org/maven/jaxme/jars/jaxme-xs-0.2.jar
> http://www.ibiblio.org/maven/jaxme/jars/jaxme-xs-SNAPSHOT.jar
>
> -Mark
>
> robert burrell donkin wrote:
>
>> hi mark
>>
>> i can see the jaxme jars on apache but not in the maven repository on
>> ibiblio. is there anything else i need to do to push the content over
>> there?
>>
>> (or have i just make some mistake in the upload...)
>>
>> - robert
>>
>> On 8 Mar 2004, at 22:20, Mark R. Diggory wrote:
>>
>>>
>>>
>>> robert burrell donkin wrote:
>>>
>>>> hi mark
>>>> i've given it a go myself but i have a few questions and i'd
>>>> appreciate it if you'd check my work so far.
>>>> On 7 Mar 2004, at 16:18, Mark R. Diggory wrote:
>>>>
>>>>> You need to establish what your groups id will be. The current
>>>>> naming trend for Apache "xml" projects has been a bit haphazard.
>>>>>
>>>>> xercies
>>>>> xml-security
>>>>> xml-resolver
>>>>> xalan
>>>>>
>>>>> Some standardization here would be good. But that will not effect
>>>>> maven.
>>>>
>>>>
>>>> i've had a chat on IRC and gone for apache-jaxme
>>>>
>>>>> There is currently a problem with Maven publishing to a BSD system
>>>>> and md5 signature generation, if you do not want to use maven to do
>>>>> the publishing then these are the tasks you need to complete:
>>>>>
>>>>> 1.) The easiest way right now is for you to place the jars into
>>>>>
>>>>> java-repository/xml-jaxme/jars/...
>>>>
>>>>
>>>> gone (but apache-jaxme rather than xml-jaxme)
>>>>
>>>>> 2.) Generate an md5 signature for each one in the same directory.
>>>>> For instance as an examples
>>>>>
>>>>> "md5 xml-jaxme-1.0.jar > xml-jaxme-1.0.jar.md5" will produce:
>>>>>
>>>>> java-repository/xml-jaxme/jars/xml-jaxme-1.0.jar
>>>>> java-repository/xml-jaxme/jars/xml-jaxme-1.0.jar.md5
>>>>
>>>>
>>>> done
>>>>
>>>>> 3.) Generate the following symlinks the above files from
>>>>>
>>>>> java-repository/xml-jaxme/jars/xml-jaxme-SNAPSHOT.jar
>>>>> java-repository/xml-jaxme/jars/xml-jaxme-SNAPSHOT.jar.md5
>>>>
>>>>
>>>> done
>>>>
>>>>> 4.) and create a file
>>>>>
>>>>> java-repository/xml-jaxme/jars/xml-jaxme-snapshot-version with the
>>>>> contents "1.0"
>>>>
>>>>
>>>> these releases are versioned 0.2: should this file contain 0.2
>>>> (since it refers to the version of the jars) or 1.0 (since it's a
>>>> mavenesque version number)
>>>
>>>
>>>
>>> It would be wise, so yes, apache-jaxme-0.2.jar
>>>
>>>>> 5.) use the following "POM" in the
>>>>>
>>>>> java-repository/xml-jaxme/poms/project/pom
>>>>> <project>
>>>>> <pomVersion>3</pomVersion>
>>>>> <id>xml-jaxme</id>
>>>>> <name>xml-jaxme</name>
>>>>> <currentVersion>1.0</currentVersion>
>>>>> <organization>
>>>>> <name>Apache Software Foundation</name>
>>>>> <url>www.apache.org</url>
>>>>> </organization>
>>>>> <licenses>
>>>>> <license>
>>>>> <name>ASL 2.0</name>
>>>>> <url>???????</url>
>>>>> <comments>???????</comments>
>>>>> </license>
>>>>> </licenses>
>>>>> </project>
>>>>
>>>>
>>>> there are a number of jar in the release. i'd been working on the
>>>> theory that each needs a separate artifact id. what should the
>>>> contents of the file be in this case?
>>>> - robert
>>>
>>>
>>>
>>> Yes, it should look like:
>>>
>>> /java-repository/apache-jaxme/jars/<artifact>-<version>.jar
>>>
>>> /java-repository/apache-jaxme/poms/project/pom
>>>
>>> <project>
>>> <pomVersion>3</pomVersion>
>>> <groupId>apache-jaxme</groupId>
>>> <name>Apache Jaxme</name>
>>> <currentVersion>0.2</currentVersion>
>>> <organization>
>>> <name>Apache Software Foundation</name>
>>> <url>www.apache.org</url>
>>> </organization>
>>> <licenses>
>>> <license>
>>> <name>ASL 2.0</name>
>>> <url>http://www.apache.org/licenses/LICENSE-2.0</url>
>>> </license>
>>> </licenses>
>>> </project>
>>>
>>> sound good, I'll take a look in the directory and verify all looks well.
>>>
>>> --
>>> Mark Diggory
>>> Software Developer
>>> Harvard MIT Data Center
>>> http://www.hmdc.harvard.edu
>>>
>>
>
--
Mark Diggory
Software Developer
Harvard MIT Data Center
http://www.hmdc.harvard.edu
Re: adding jaxme jars
Posted by Sander Striker <st...@apache.org>.
On Thu, 2004-03-11 at 01:18, Mark R. Diggory wrote:
> Robert, the jars are there, we should probably do a little renaming. My
> fault for not looking yesterday.
Ok, I'm going to ask again nicely: please think about a naming scheme
long and hard, _then_ implement it. Doing it by trial and error, moving
things around is not nice on our mirrors. And wasteful on top of that.
It would be helpful if a document was created similar to
http://www.apache.org/dev/mirrors.html, which you can point people to
when they are wondering what their release should look like in the
java-repository.
Thanks,
Sander
Re: adding jaxme jars
Posted by robert burrell donkin <rd...@apache.org>.
On 12 Mar 2004, at 01:09, Mark R. Diggory wrote:
<snip>
> 2.) It's next to impossible to enforce a directory structure/naming
> policy with the contents of the directories writable (let alone the
> fact that its an actual directory structure). Even those intimate with
> the project and effort end up doing things they consider minor which
> in turn effect the entire community adversely.
it wouldn't be unreasonable to request that infrastructure create a
group for the repository administrators.
mark - what's the current status?
(i'd like to be able to use these jars in a jelly tag library.)
i'm a bit confused because the jar's were simply unpacked from the
tar-balled 0.2 incubation release. there has been a vote in the ws pmc
but i'm also more than a little unclear as to why a separate release
vote is necessary for adding jars which have already been released into
the repository. is this also the case for new releases? (for example,
would separate pmc votes be required to release the jaxme 0.3
distributions and to add the jar within them to the repository?)
BTW i do appreciate you work in getting the repository up and running.
these kinds of roles are difficult and energy sapping but are important
to the ASF.
- robert
Re: adding jaxme jars
Posted by "Mark R. Diggory" <md...@latte.harvard.edu>.
Noel J. Bergman wrote:
>>sander's post early on this thread (quite reasonably) suggested that
>>it'd be a good idea for the repository team to think about how to
>>handle incubating projects in general (before any more come along). i
>>think that sounds like a very reasonable plan.
>
>
> Agreed. And it would be helpful if the Repository team was aware, as the
> rest of infrastructure is, that releases must be voted on by a PMC. If
> there is a request for publication, it should be cc'd to the PMC and made
> sure that the PMC doesn't raise a flag. That's the same as we do when
> creating new accounts, lists, etc.
>
Yes, I probably have been a little ambitious in placing content in the
repository. I will yield 100% to whatever policies we invoke concerning
publishing of jar's in accordance with the PMC's.
1.) I think we should really have an effort now set though the next
level of cleanup --> moving the build-versions that are in the
repository off into cvs.apache.org
2.) It's next to impossible to enforce a directory structure/naming
policy with the contents of the directories writable (let alone the fact
that its an actual directory structure). Even those intimate with the
project and effort end up doing things they consider minor which in turn
effect the entire community adversely.
> One factor, unique to the Incubator, is that we have a concept known as a
> PPMC, which consists of the PMC and others. For a release, we should make
> sure that the both the PPMC and PMC mailing lists are cc'd.
>
Yes, once a system is established. I think this should be a process
which the Release Manager for a project and their PMC complete. We
should eventually setup a policy whereby no one from the Repository
group actually "Publishes Releases" and instead plays a more "advisory"
and "maintenance" role in terms of the repository.
>
>>it also seems to me (at least) that it's really the incubator pmc who
>>are the right people to ask about the management of releases created
>>whilst under incubation (including any special measures that might be
>>required for jars released whilst in incubation).
>
>
> Absolutely. However, in this specific case, JaxMe has been voted to the WS
> PMC, who will be responsible for it.
>
> --- Noel
I've contacted the WS group more formally to discuss this on the
general@ws.apache.org mailing list.
-Mark
--
Mark Diggory
Software Developer
Harvard MIT Data Center
http://www.hmdc.harvard.edu
Re: adding jaxme jars
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Noel J. Bergman wrote:
>>sander's post early on this thread (quite reasonably) suggested that
>>it'd be a good idea for the repository team to think about how to
>>handle incubating projects in general (before any more come along). i
>>think that sounds like a very reasonable plan.
>
> Agreed. And it would be helpful if the Repository team was aware, as the
> rest of infrastructure is, that releases must be voted on by a PMC. If
> there is a request for publication, it should be cc'd to the PMC and made
> sure that the PMC doesn't raise a flag. That's the same as we do when
> creating new accounts, lists, etc.
BTW, this is a reason IMHO that shows how a notifocation system can
increase the control loop over what we publish.
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
RE: adding jaxme jars
Posted by "Noel J. Bergman" <no...@devtech.com>.
> sander's post early on this thread (quite reasonably) suggested that
> it'd be a good idea for the repository team to think about how to
> handle incubating projects in general (before any more come along). i
> think that sounds like a very reasonable plan.
Agreed. And it would be helpful if the Repository team was aware, as the
rest of infrastructure is, that releases must be voted on by a PMC. If
there is a request for publication, it should be cc'd to the PMC and made
sure that the PMC doesn't raise a flag. That's the same as we do when
creating new accounts, lists, etc.
One factor, unique to the Incubator, is that we have a concept known as a
PPMC, which consists of the PMC and others. For a release, we should make
sure that the both the PPMC and PMC mailing lists are cc'd.
> it also seems to me (at least) that it's really the incubator pmc who
> are the right people to ask about the management of releases created
> whilst under incubation (including any special measures that might be
> required for jars released whilst in incubation).
Absolutely. However, in this specific case, JaxMe has been voted to the WS
PMC, who will be responsible for it.
--- Noel
Re: adding jaxme jars
Posted by robert burrell donkin <rd...@apache.org>.
hi noel
sander's post early on this thread (quite reasonably) suggested that
it'd be a good idea for the repository team to think about how to
handle incubating projects in general (before any more come along). i
think that sounds like a very reasonable plan.
it also seems to me (at least) that it's really the incubator pmc who
are the right people to ask about the management of releases created
whilst under incubation (including any special measures that might be
required for jars released whilst in incubation).
- robert
On 11 Mar 2004, at 21:15, Noel J. Bergman wrote:
> I would expect JaxMe to be released by the WS PMC. You should raise
> any
> issue with them.
>
> --- Noel
>
> -----Original Message-----
> From: Mark R. Diggory [mailto:mdiggory@latte.harvard.edu]
> Sent: Thursday, March 11, 2004 16:00
> To: repository@apache.org
> Subject: Re: adding jaxme jars
>
>
> Is there just an issue with where its going to be located then? (I.E.
> site, cvs/svn location and distribution directories)? I'm very
> unfamiliar with the Incubator and its policies so excuse my naivety.
> Once a project has graduated via Vote, is there a process for its
> "migration"? I think this was possibly Roberts point.
>
> -Mark
>
Re: adding jaxme jars
Posted by robert burrell donkin <rd...@apache.org>.
hi jochen
(here's a potted summary, hopefully other people will jump in and
correct any mistakes i make)
maven is a declarative project management tool (from apache) which is
used by a number of jakarta products (amongst others). for products
built with maven, correctly named jars must be made available from a
repository so that maven can download them (as needed). products
created by the ASF should be released via the java repository which is
being created by the repository work group. things are just getting
going so there are a few teething problems with this new process.
i have some jelly tag libraries for JaxMe but jelly is mavenized and so
before i can commit them, the last jaxme release needed uploading to
the new repository. (once i have these new jelly tag libraries, i can
push forward and create a maven plugging which will allow mavenized
builds to use jaxme.) unfortunately, we managed to get our wires
crossed a little and some aspects of the process still need to be
developed for incubating projects.
we're just trying to sort the mess out. feel free to join in :)
- robert
On 12 Mar 2004, at 07:36, Jochen Wiedmann wrote:
>
> Sorry for asking newbie questions, but as I should most probably
> take some responsibility on this issue: Could someone be so kind
> as to explain me what the question is and what decisions have to
> be taken?
>
>
> Regards,
>
> Jochen
>
>
> Zitat von "Noel J. Bergman" <no...@devtech.com>:
>
>> I would expect JaxMe to be released by the WS PMC. You should raise
>> any
>> issue with them.
>>
>> --- Noel
>>
>> -----Original Message-----
>> From: Mark R. Diggory [mailto:mdiggory@latte.harvard.edu]
>> Sent: Thursday, March 11, 2004 16:00
>> To: repository@apache.org
>> Subject: Re: adding jaxme jars
>>
>>
>> Is there just an issue with where its going to be located then? (I.E.
>> site, cvs/svn location and distribution directories)? I'm very
>> unfamiliar with the Incubator and its policies so excuse my naivety.
>> Once a project has graduated via Vote, is there a process for its
>> "migration"? I think this was possibly Roberts point.
>>
>> -Mark
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: pmc-unsubscribe@ws.apache.org
>> For additional commands, e-mail: pmc-help@ws.apache.org
>>
>>
>>
>
>
>
RE: adding jaxme jars
Posted by Jochen Wiedmann <jo...@ispsoft.de>.
Sorry for asking newbie questions, but as I should most probably
take some responsibility on this issue: Could someone be so kind
as to explain me what the question is and what decisions have to
be taken?
Regards,
Jochen
Zitat von "Noel J. Bergman" <no...@devtech.com>:
> I would expect JaxMe to be released by the WS PMC. You should raise any
> issue with them.
>
> --- Noel
>
> -----Original Message-----
> From: Mark R. Diggory [mailto:mdiggory@latte.harvard.edu]
> Sent: Thursday, March 11, 2004 16:00
> To: repository@apache.org
> Subject: Re: adding jaxme jars
>
>
> Is there just an issue with where its going to be located then? (I.E.
> site, cvs/svn location and distribution directories)? I'm very
> unfamiliar with the Incubator and its policies so excuse my naivety.
> Once a project has graduated via Vote, is there a process for its
> "migration"? I think this was possibly Roberts point.
>
> -Mark
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: pmc-unsubscribe@ws.apache.org
> For additional commands, e-mail: pmc-help@ws.apache.org
>
>
>
RE: adding jaxme jars
Posted by "Noel J. Bergman" <no...@devtech.com>.
I would expect JaxMe to be released by the WS PMC. You should raise any
issue with them.
--- Noel
-----Original Message-----
From: Mark R. Diggory [mailto:mdiggory@latte.harvard.edu]
Sent: Thursday, March 11, 2004 16:00
To: repository@apache.org
Subject: Re: adding jaxme jars
Is there just an issue with where its going to be located then? (I.E.
site, cvs/svn location and distribution directories)? I'm very
unfamiliar with the Incubator and its policies so excuse my naivety.
Once a project has graduated via Vote, is there a process for its
"migration"? I think this was possibly Roberts point.
-Mark
Re: adding jaxme jars
Posted by "Mark R. Diggory" <md...@latte.harvard.edu>.
Is there just an issue with where its going to be located then? (I.E.
site, cvs/svn location and distribution directories)? I'm very
unfamiliar with the Incubator and its policies so excuse my naivety.
Once a project has graduated via Vote, is there a process for its
"migration"? I think this was possibly Roberts point.
-Mark
Noel J. Bergman wrote:
>>jaxme would have been out of incubation by now but there are some major
>>hassles with procedure.
>
>
> No, there was a vote taken. It was then redone a day later in a public
> forum. Hardly a major hassle, nor a significant delay.
>
> --- Noel
>
--
Mark Diggory
Software Developer
Harvard MIT Data Center
http://www.hmdc.harvard.edu
Re: adding jaxme jars
Posted by robert burrell donkin <rd...@apache.org>.
roy's post (which was the last one on this subject on the lists i'm
subscribed to) gave the impression that the procedural problem was
reasonable major. i'm glad that it's turned out not to be.
- robert
On 11 Mar 2004, at 20:54, Noel J. Bergman wrote:
>> jaxme would have been out of incubation by now but there are some
>> major
>> hassles with procedure.
>
> No, there was a vote taken. It was then redone a day later in a public
> forum. Hardly a major hassle, nor a significant delay.
>
> --- Noel
>
RE: adding jaxme jars
Posted by "Noel J. Bergman" <no...@devtech.com>.
> jaxme would have been out of incubation by now but there are some major
> hassles with procedure.
No, there was a vote taken. It was then redone a day later in a public
forum. Hardly a major hassle, nor a significant delay.
--- Noel
Re: adding jaxme jars
Posted by robert burrell donkin <rd...@apache.org>.
On 11 Mar 2004, at 19:59, Mark R. Diggory wrote:
> Sander Striker wrote:
>>> From: Mark R. Diggory [mailto:mdiggory@latte.harvard.edu]
<snip>
>>> So, if your going to be distributing a "build release" I recommend
>>> the naming strategy where all artifactID's match. If the jaxme
>>> project is planning to leave the incubator anytime in the future, I
>>> would highly recommend you not use the word "incubator" in the
>>> artifact id. My personal opinion added to this is that its the same
>>> way we don't use "jakarta" in in projects like the Jakarta Commons,
>>> because some aspects Jakarta is a Foundry. Incubator is also a
>>> Foundry.
>> Incubator is a bit of a different beast than Jakarta. Projects in
>> the Incubator are not 'full fledged ASF projects' yet, they will be
>> as soon as they leave in Incubator. The incubation designation
>> has come up on the general@incubator list. If this is problematic
>> for any reason I suggest you bring that up there.
>
> Sounds similar to the Jakarta Commons Sandbox, Actually, projects
> there are not allowed to release jars until they graduate to the
> Jakarta Commons Proper. Generally speaking, jars produce by such
> projects are not distributed anywhere but by the author on their local
> system. Yet, I believe that Jakarta does complete a daily build
> process for these projects as well, so even though they are not
> officially released, there are packages which can be gotten at on
> cvs.apache.org.
AIUI the incubator is a bit of a special case. the ASF does not allow
full official releases from the incubator but does allow versioned
incubation releases provided that it's made clear these are incubation
releases. (if this sounds a little hazy, that's because i haven't
really kept up with the development of the incubation processes.)
jaxme would have been out of incubation by now but there are some major
hassles with procedure. (there appear to be some disputes amongst the
pmc members about the voting process. hopefully these will be resolved
sometime very soon.) so, it's probably best to go with the naming
schema mark suggests for jaxme but maybe to ask about the incubator's
policy on jar naming the general list.
- robert
Re: adding jaxme jars
Posted by "Mark R. Diggory" <md...@latte.harvard.edu>.
Sander Striker wrote:
>>From: Mark R. Diggory [mailto:mdiggory@latte.harvard.edu]
>>Sent: Thursday, March 11, 2004 7:52 PM
>
>
>>Basically, in Maven the difference between "version releases" and "build
>>releases" is designated in the version, not in the artifact id.
>>
>>/jaxme/jars/jaxme-<build-date>.jar
>>
>>and
>>
>>/jaxme/jars/jaxme-<version-no>.jar
>>
>>It is important to have your artifactId's match across all versions of
>>an artifact, otherwise they aren't the same "artifact", so
>>
>>/jaxme/jars/jaxme-incubator-x.x.jar
>>
>>does not share the same artifact id as
>>
>>/jaxme/jars/jaxme-SNAPSHOT.jar
>>
>>to have them match it would have to be
>>
>>/jaxme/jars/jaxme-incubator-SNAPSHOT.jar
>
>
> Hmm, couldn't the filename and artifact id be decoupled?
>
I'm not suggesting rightness or wrongness of the approach in the
following comments. Simply just what Maven currently does:
This naming structure is important only in terms of the existing Maven
Repository Design (probably less likely in future Maven2 designs). The
repository structure for Maven is currently rather strict in this regard
<repository>/<groupId>/<type>/<artifactId>-<version>.<ext>
One question: How would you then "lookup" that file by only "group",
"artifact" and "version"? You'd need to know how to generate its
"filename" (ie in this case:<artifactId>-<version>.<ext>).
When ever I think about this, I always come full circle that the only
"flexible" solution to this sort of issue is not in the URL "syntax" but
in the "resolution" mechanism. What we are essentially doing is trying
to establish an "Identifier" for a resource that can be "resolved" to
that resource.
I'm really getting more and more of the opinion that what
Apache/Maven/Depot etc. needs more than a "Repository" structure is a
"resolving service". A service very much similar in structure to that
which "Public Id's" in XML/SGML or DOI's/Handles/Purl's in the Library
community. Then a Project is simply assigned a Public Id Namespace in
which to "identify" its resources, Then resolver/proxy services can be
used to map that "id" to an actual URL location of the file. A url
location that can be "anywhere" and of "any format". Then the
"structure" of these directories become loose and simply just for
managing a projects released files again.
http://www.handle.net
http://www.purl.org
http://www.doi.org
http://www.dspace.org
Think about it, This gives us a layer of "flexibility" in resolution
which is "decoupled" from the layer of storage. As such files can move
around and files can be located in multiple locations (mirrors). The
resolving mechanism handles the persistence of the id.
This way, if (for instance) a jar file is "demoted" from public
distribution (aka www.apache.org/dist) on the mirrors, its id simply is
pointed at the archived version instead of the mirrored version.
And, if a file is mirrored, the id can be resolved using a mechanism
similar to "/dyn/closer.cgi" to resolve to a distribution mirror for
that resource instead of the Apache server.
>
>>So, if your going to be distributing a "build release" I recommend the
>>naming strategy where all artifactID's match. If the jaxme project is
>>planning to leave the incubator anytime in the future, I would highly
>>recommend you not use the word "incubator" in the artifact id. My
>>personal opinion added to this is that its the same way we don't use
>>"jakarta" in in projects like the Jakarta Commons, because some aspects
>>Jakarta is a Foundry. Incubator is also a Foundry.
>
>
> Incubator is a bit of a different beast than Jakarta. Projects in
> the Incubator are not 'full fledged ASF projects' yet, they will be
> as soon as they leave in Incubator. The incubation designation
> has come up on the general@incubator list. If this is problematic
> for any reason I suggest you bring that up there.
>
Sounds similar to the Jakarta Commons Sandbox, Actually, projects there
are not allowed to release jars until they graduate to the Jakarta
Commons Proper. Generally speaking, jars produce by such projects are
not distributed anywhere but by the author on their local system. Yet, I
believe that Jakarta does complete a daily build process for these
projects as well, so even though they are not officially released, there
are packages which can be gotten at on cvs.apache.org.
>
>>My future planned strategy to support "build-releases" is to have build
>>releases (daily, weekly builds etc) not be present on:
>>
>>/www/www.apache.org/dist/java-repository
>>
>>but to actually be present on:
>>
>>/www/cvs.apache.org/builds/java-repository
>
>
> Which is where they belong. Snapshots don't ever belong on
> www.apache.org/dist/.
>
Absolutely Correct.
>
>>Then, to actually use this approach with Maven you'd have to add the
>>cvs.apache.org repository to your Maven client, this makes project
>>dependencies hairy in the Current release of Maven because the contents
>>wouldn't be present at ibiblio. We still have much to decide to do and
>>infrastructure to setup to have this build location.
>
>
> Is there some roadmap I can read and comment on?
>
Unfortunately, no. Only the discussion on this list to date.
>
>>My current strategy in this case is to have the build-releases in the
>>same project directory as the version releases, then they are all
>>rsynced with ibiblio properly. This is simply because build releases
>>already existed in the repository when we moved the apache contents of
>>ibiblio back to Apache.
>>
>>What is the status of jaxme in the incubator? When do they anticipate an
>>official release?
>
>
> Given there will be future projects in incubator with releases during
> incubation, it would be nice if we could accomodate for that.
>
I think a repository structure in the cvs.apache.org/builds area should
be reserved for this.
>
>>Maybe this is a reason enough to push forward the development of the
>>daily/weekly/... build repository. Allowing any more build-releasing in
>>the dist/java-repository is a sensitive issue when it comes to
>>mirroring. It would be wise for us to stop doing this asap. This is
>>probably a good location where I could use assistance from repository
>>folks in working out these details.
>
>
>
> Sander
Should we setup a Maven repository structure in cvs.apache.org/build to
publish snapshot jars to now? This would at least get the ball rolling.
-Mark
--
Mark Diggory
Software Developer
Harvard MIT Data Center
http://www.hmdc.harvard.edu
RE: adding jaxme jars
Posted by Sander Striker <st...@apache.org>.
> From: Mark R. Diggory [mailto:mdiggory@latte.harvard.edu]
> Sent: Thursday, March 11, 2004 7:52 PM
> Basically, in Maven the difference between "version releases" and "build
> releases" is designated in the version, not in the artifact id.
>
> /jaxme/jars/jaxme-<build-date>.jar
>
> and
>
> /jaxme/jars/jaxme-<version-no>.jar
>
> It is important to have your artifactId's match across all versions of
> an artifact, otherwise they aren't the same "artifact", so
>
> /jaxme/jars/jaxme-incubator-x.x.jar
>
> does not share the same artifact id as
>
> /jaxme/jars/jaxme-SNAPSHOT.jar
>
> to have them match it would have to be
>
> /jaxme/jars/jaxme-incubator-SNAPSHOT.jar
Hmm, couldn't the filename and artifact id be decoupled?
> So, if your going to be distributing a "build release" I recommend the
> naming strategy where all artifactID's match. If the jaxme project is
> planning to leave the incubator anytime in the future, I would highly
> recommend you not use the word "incubator" in the artifact id. My
> personal opinion added to this is that its the same way we don't use
> "jakarta" in in projects like the Jakarta Commons, because some aspects
> Jakarta is a Foundry. Incubator is also a Foundry.
Incubator is a bit of a different beast than Jakarta. Projects in
the Incubator are not 'full fledged ASF projects' yet, they will be
as soon as they leave in Incubator. The incubation designation
has come up on the general@incubator list. If this is problematic
for any reason I suggest you bring that up there.
> My future planned strategy to support "build-releases" is to have build
> releases (daily, weekly builds etc) not be present on:
>
> /www/www.apache.org/dist/java-repository
>
> but to actually be present on:
>
> /www/cvs.apache.org/builds/java-repository
Which is where they belong. Snapshots don't ever belong on
www.apache.org/dist/.
> Then, to actually use this approach with Maven you'd have to add the
> cvs.apache.org repository to your Maven client, this makes project
> dependencies hairy in the Current release of Maven because the contents
> wouldn't be present at ibiblio. We still have much to decide to do and
> infrastructure to setup to have this build location.
Is there some roadmap I can read and comment on?
> My current strategy in this case is to have the build-releases in the
> same project directory as the version releases, then they are all
> rsynced with ibiblio properly. This is simply because build releases
> already existed in the repository when we moved the apache contents of
> ibiblio back to Apache.
>
> What is the status of jaxme in the incubator? When do they anticipate an
> official release?
Given there will be future projects in incubator with releases during
incubation, it would be nice if we could accomodate for that.
> Maybe this is a reason enough to push forward the development of the
> daily/weekly/... build repository. Allowing any more build-releasing in
> the dist/java-repository is a sensitive issue when it comes to
> mirroring. It would be wise for us to stop doing this asap. This is
> probably a good location where I could use assistance from repository
> folks in working out these details.
Sander
Re: adding jaxme jars
Posted by "Mark R. Diggory" <md...@latte.harvard.edu>.
Basically, in Maven the difference between "version releases" and "build
releases" is designated in the version, not in the artifact id.
/jaxme/jars/jaxme-<build-date>.jar
and
/jaxme/jars/jaxme-<version-no>.jar
It is important to have your artifactId's match across all versions of
an artifact, otherwise they aren't the same "artifact", so
/jaxme/jars/jaxme-incubator-x.x.jar
does not share the same artifact id as
/jaxme/jars/jaxme-SNAPSHOT.jar
to have them match it would have to be
/jaxme/jars/jaxme-incubator-SNAPSHOT.jar
So, if your going to be distributing a "build release" I recommend the
naming strategy where all artifactID's match. If the jaxme project is
planning to leave the incubator anytime in the future, I would highly
recommend you not use the word "incubator" in the artifact id. My
personal opinion added to this is that its the same way we don't use
"jakarta" in in projects like the Jakarta Commons, because some aspects
Jakarta is a Foundry. Incubator is also a Foundry.
My future planned strategy to support "build-releases" is to have build
releases (daily, weekly builds etc) not be present on:
/www/www.apache.org/dist/java-repository
but to actually be present on:
/www/cvs.apache.org/builds/java-repository
Then, to actually use this approach with Maven you'd have to add the
cvs.apache.org repository to your Maven client, this makes project
dependencies hairy in the Current release of Maven because the contents
wouldn't be present at ibiblio. We still have much to decide to do and
infrastructure to setup to have this build location.
My current strategy in this case is to have the build-releases in the
same project directory as the version releases, then they are all
rsynced with ibiblio properly. This is simply because build releases
already existed in the repository when we moved the apache contents of
ibiblio back to Apache.
What is the status of jaxme in the incubator? When do they anticipate an
official release?
Maybe this is a reason enough to push forward the development of the
daily/weekly/... build repository. Allowing any more build-releasing in
the dist/java-repository is a sensitive issue when it comes to
mirroring. It would be wise for us to stop doing this asap. This is
probably a good location where I could use assistance from repository
folks in working out these details.
-Mark
robert burrell donkin wrote:
> hi mark
>
> the release in question was made whilst jaxme was in the incubator. AIUI
> it's an important requirement that it's clear that these are not
> official ASF releases but incubation releases. the most direct way to do
> this seemed (to me) to be continue to use the naming convention used by
> incubation releases.
>
> - robert
>
> On 11 Mar 2004, at 00:18, Mark R. Diggory wrote:
>
>> Robert, the jars are there, we should probably do a little renaming.
>> My fault for not looking yesterday.
>>
>> http://www.ibiblio.org/maven/apache-jaxme/jars/
>> !!!!!!!!!!
>> http://www.ibiblio.org/maven/apache-jaxme/jars/jaxme-incubation-0.2.jar
>>
>> we should probably have it more simply be
>>
>> http://www.ibiblio.org/maven/jaxme/jars/jaxme-0.2.jar
>> http://www.ibiblio.org/maven/jaxme/jars/jaxme-SNAPSHOT.jar
>>
>> http://www.ibiblio.org/maven/jaxme/jars/jaxme-rt-0.2.jar
>> http://www.ibiblio.org/maven/jaxme/jars/jaxme-rt-SNAPSHOT.jar
>>
>> http://www.ibiblio.org/maven/jaxme/jars/jaxme-api-0.2.jar
>> http://www.ibiblio.org/maven/jaxme/jars/jaxme-api-SNAPSHOT.jar
>>
>> http://www.ibiblio.org/maven/jaxme/jars/jaxme-js-0.2.jar
>> http://www.ibiblio.org/maven/jaxme/jars/jaxme-js-SNAPSHOT.jar
>>
>> http://www.ibiblio.org/maven/jaxme/jars/jaxme-pm-0.2.jar
>> http://www.ibiblio.org/maven/jaxme/jars/jaxme-pm-SNAPSHOT.jar
>>
>> http://www.ibiblio.org/maven/jaxme/jars/jaxme-xs-0.2.jar
>> http://www.ibiblio.org/maven/jaxme/jars/jaxme-xs-SNAPSHOT.jar
>>
>> -Mark
>>
>> robert burrell donkin wrote:
>>
>>> hi mark
>>> i can see the jaxme jars on apache but not in the maven repository on
>>> ibiblio. is there anything else i need to do to push the content over
>>> there?
>>> (or have i just make some mistake in the upload...)
>>> - robert
>>> On 8 Mar 2004, at 22:20, Mark R. Diggory wrote:
>>>
>>>>
>>>>
>>>> robert burrell donkin wrote:
>>>>
>>>>> hi mark
>>>>> i've given it a go myself but i have a few questions and i'd
>>>>> appreciate it if you'd check my work so far.
>>>>> On 7 Mar 2004, at 16:18, Mark R. Diggory wrote:
>>>>>
>>>>>> You need to establish what your groups id will be. The current
>>>>>> naming trend for Apache "xml" projects has been a bit haphazard.
>>>>>>
>>>>>> xercies
>>>>>> xml-security
>>>>>> xml-resolver
>>>>>> xalan
>>>>>>
>>>>>> Some standardization here would be good. But that will not effect
>>>>>> maven.
>>>>>
>>>>>
>>>>> i've had a chat on IRC and gone for apache-jaxme
>>>>>
>>>>>> There is currently a problem with Maven publishing to a BSD system
>>>>>> and md5 signature generation, if you do not want to use maven to
>>>>>> do the publishing then these are the tasks you need to complete:
>>>>>>
>>>>>> 1.) The easiest way right now is for you to place the jars into
>>>>>>
>>>>>> java-repository/xml-jaxme/jars/...
>>>>>
>>>>>
>>>>> gone (but apache-jaxme rather than xml-jaxme)
>>>>>
>>>>>> 2.) Generate an md5 signature for each one in the same directory.
>>>>>> For instance as an examples
>>>>>>
>>>>>> "md5 xml-jaxme-1.0.jar > xml-jaxme-1.0.jar.md5" will produce:
>>>>>>
>>>>>> java-repository/xml-jaxme/jars/xml-jaxme-1.0.jar
>>>>>> java-repository/xml-jaxme/jars/xml-jaxme-1.0.jar.md5
>>>>>
>>>>>
>>>>> done
>>>>>
>>>>>> 3.) Generate the following symlinks the above files from
>>>>>>
>>>>>> java-repository/xml-jaxme/jars/xml-jaxme-SNAPSHOT.jar
>>>>>> java-repository/xml-jaxme/jars/xml-jaxme-SNAPSHOT.jar.md5
>>>>>
>>>>>
>>>>> done
>>>>>
>>>>>> 4.) and create a file
>>>>>>
>>>>>> java-repository/xml-jaxme/jars/xml-jaxme-snapshot-version with the
>>>>>> contents "1.0"
>>>>>
>>>>>
>>>>> these releases are versioned 0.2: should this file contain 0.2
>>>>> (since it refers to the version of the jars) or 1.0 (since it's a
>>>>> mavenesque version number)
>>>>
>>>>
>>>>
>>>> It would be wise, so yes, apache-jaxme-0.2.jar
>>>>
>>>>>> 5.) use the following "POM" in the
>>>>>>
>>>>>> java-repository/xml-jaxme/poms/project/pom
>>>>>> <project>
>>>>>> <pomVersion>3</pomVersion>
>>>>>> <id>xml-jaxme</id>
>>>>>> <name>xml-jaxme</name>
>>>>>> <currentVersion>1.0</currentVersion>
>>>>>> <organization>
>>>>>> <name>Apache Software Foundation</name>
>>>>>> <url>www.apache.org</url>
>>>>>> </organization>
>>>>>> <licenses>
>>>>>> <license>
>>>>>> <name>ASL 2.0</name>
>>>>>> <url>???????</url>
>>>>>> <comments>???????</comments>
>>>>>> </license>
>>>>>> </licenses>
>>>>>> </project>
>>>>>
>>>>>
>>>>> there are a number of jar in the release. i'd been working on the
>>>>> theory that each needs a separate artifact id. what should the
>>>>> contents of the file be in this case?
>>>>> - robert
>>>>
>>>>
>>>>
>>>> Yes, it should look like:
>>>>
>>>> /java-repository/apache-jaxme/jars/<artifact>-<version>.jar
>>>>
>>>> /java-repository/apache-jaxme/poms/project/pom
>>>>
>>>> <project>
>>>> <pomVersion>3</pomVersion>
>>>> <groupId>apache-jaxme</groupId>
>>>> <name>Apache Jaxme</name>
>>>> <currentVersion>0.2</currentVersion>
>>>> <organization>
>>>> <name>Apache Software Foundation</name>
>>>> <url>www.apache.org</url>
>>>> </organization>
>>>> <licenses>
>>>> <license>
>>>> <name>ASL 2.0</name>
>>>> <url>http://www.apache.org/licenses/LICENSE-2.0</url>
>>>> </license>
>>>> </licenses>
>>>> </project>
>>>>
>>>> sound good, I'll take a look in the directory and verify all looks
>>>> well.
>>>>
>>>> --
>>>> Mark Diggory
>>>> Software Developer
>>>> Harvard MIT Data Center
>>>> http://www.hmdc.harvard.edu
>>>>
>>
>> --
>> Mark Diggory
>> Software Developer
>> Harvard MIT Data Center
>> http://www.hmdc.harvard.edu
>>
>
--
Mark Diggory
Software Developer
Harvard MIT Data Center
http://www.hmdc.harvard.edu
Re: adding jaxme jars
Posted by robert burrell donkin <rd...@apache.org>.
hi mark
the release in question was made whilst jaxme was in the incubator.
AIUI it's an important requirement that it's clear that these are not
official ASF releases but incubation releases. the most direct way to
do this seemed (to me) to be continue to use the naming convention used
by incubation releases.
- robert
On 11 Mar 2004, at 00:18, Mark R. Diggory wrote:
> Robert, the jars are there, we should probably do a little renaming.
> My fault for not looking yesterday.
>
> http://www.ibiblio.org/maven/apache-jaxme/jars/
> !!!!!!!!!!
> http://www.ibiblio.org/maven/apache-jaxme/jars/jaxme-incubation-0.2.jar
>
> we should probably have it more simply be
>
> http://www.ibiblio.org/maven/jaxme/jars/jaxme-0.2.jar
> http://www.ibiblio.org/maven/jaxme/jars/jaxme-SNAPSHOT.jar
>
> http://www.ibiblio.org/maven/jaxme/jars/jaxme-rt-0.2.jar
> http://www.ibiblio.org/maven/jaxme/jars/jaxme-rt-SNAPSHOT.jar
>
> http://www.ibiblio.org/maven/jaxme/jars/jaxme-api-0.2.jar
> http://www.ibiblio.org/maven/jaxme/jars/jaxme-api-SNAPSHOT.jar
>
> http://www.ibiblio.org/maven/jaxme/jars/jaxme-js-0.2.jar
> http://www.ibiblio.org/maven/jaxme/jars/jaxme-js-SNAPSHOT.jar
>
> http://www.ibiblio.org/maven/jaxme/jars/jaxme-pm-0.2.jar
> http://www.ibiblio.org/maven/jaxme/jars/jaxme-pm-SNAPSHOT.jar
>
> http://www.ibiblio.org/maven/jaxme/jars/jaxme-xs-0.2.jar
> http://www.ibiblio.org/maven/jaxme/jars/jaxme-xs-SNAPSHOT.jar
>
> -Mark
>
> robert burrell donkin wrote:
>
>> hi mark
>> i can see the jaxme jars on apache but not in the maven repository on
>> ibiblio. is there anything else i need to do to push the content over
>> there?
>> (or have i just make some mistake in the upload...)
>> - robert
>> On 8 Mar 2004, at 22:20, Mark R. Diggory wrote:
>>>
>>>
>>> robert burrell donkin wrote:
>>>
>>>> hi mark
>>>> i've given it a go myself but i have a few questions and i'd
>>>> appreciate it if you'd check my work so far.
>>>> On 7 Mar 2004, at 16:18, Mark R. Diggory wrote:
>>>>
>>>>> You need to establish what your groups id will be. The current
>>>>> naming trend for Apache "xml" projects has been a bit haphazard.
>>>>>
>>>>> xercies
>>>>> xml-security
>>>>> xml-resolver
>>>>> xalan
>>>>>
>>>>> Some standardization here would be good. But that will not effect
>>>>> maven.
>>>>
>>>> i've had a chat on IRC and gone for apache-jaxme
>>>>
>>>>> There is currently a problem with Maven publishing to a BSD system
>>>>> and md5 signature generation, if you do not want to use maven to
>>>>> do the publishing then these are the tasks you need to complete:
>>>>>
>>>>> 1.) The easiest way right now is for you to place the jars into
>>>>>
>>>>> java-repository/xml-jaxme/jars/...
>>>>
>>>> gone (but apache-jaxme rather than xml-jaxme)
>>>>
>>>>> 2.) Generate an md5 signature for each one in the same directory.
>>>>> For instance as an examples
>>>>>
>>>>> "md5 xml-jaxme-1.0.jar > xml-jaxme-1.0.jar.md5" will produce:
>>>>>
>>>>> java-repository/xml-jaxme/jars/xml-jaxme-1.0.jar
>>>>> java-repository/xml-jaxme/jars/xml-jaxme-1.0.jar.md5
>>>>
>>>> done
>>>>
>>>>> 3.) Generate the following symlinks the above files from
>>>>>
>>>>> java-repository/xml-jaxme/jars/xml-jaxme-SNAPSHOT.jar
>>>>> java-repository/xml-jaxme/jars/xml-jaxme-SNAPSHOT.jar.md5
>>>>
>>>> done
>>>>
>>>>> 4.) and create a file
>>>>>
>>>>> java-repository/xml-jaxme/jars/xml-jaxme-snapshot-version with the
>>>>> contents "1.0"
>>>>
>>>> these releases are versioned 0.2: should this file contain 0.2
>>>> (since it refers to the version of the jars) or 1.0 (since it's a
>>>> mavenesque version number)
>>>
>>>
>>> It would be wise, so yes, apache-jaxme-0.2.jar
>>>
>>>>> 5.) use the following "POM" in the
>>>>>
>>>>> java-repository/xml-jaxme/poms/project/pom
>>>>> <project>
>>>>> <pomVersion>3</pomVersion>
>>>>> <id>xml-jaxme</id>
>>>>> <name>xml-jaxme</name>
>>>>> <currentVersion>1.0</currentVersion>
>>>>> <organization>
>>>>> <name>Apache Software Foundation</name>
>>>>> <url>www.apache.org</url>
>>>>> </organization>
>>>>> <licenses>
>>>>> <license>
>>>>> <name>ASL 2.0</name>
>>>>> <url>???????</url>
>>>>> <comments>???????</comments>
>>>>> </license>
>>>>> </licenses>
>>>>> </project>
>>>>
>>>> there are a number of jar in the release. i'd been working on the
>>>> theory that each needs a separate artifact id. what should the
>>>> contents of the file be in this case?
>>>> - robert
>>>
>>>
>>> Yes, it should look like:
>>>
>>> /java-repository/apache-jaxme/jars/<artifact>-<version>.jar
>>>
>>> /java-repository/apache-jaxme/poms/project/pom
>>>
>>> <project>
>>> <pomVersion>3</pomVersion>
>>> <groupId>apache-jaxme</groupId>
>>> <name>Apache Jaxme</name>
>>> <currentVersion>0.2</currentVersion>
>>> <organization>
>>> <name>Apache Software Foundation</name>
>>> <url>www.apache.org</url>
>>> </organization>
>>> <licenses>
>>> <license>
>>> <name>ASL 2.0</name>
>>> <url>http://www.apache.org/licenses/LICENSE-2.0</url>
>>> </license>
>>> </licenses>
>>> </project>
>>>
>>> sound good, I'll take a look in the directory and verify all looks
>>> well.
>>>
>>> --
>>> Mark Diggory
>>> Software Developer
>>> Harvard MIT Data Center
>>> http://www.hmdc.harvard.edu
>>>
>
> --
> Mark Diggory
> Software Developer
> Harvard MIT Data Center
> http://www.hmdc.harvard.edu
>
Re: adding jaxme jars
Posted by "Mark R. Diggory" <md...@latte.harvard.edu>.
Robert, the jars are there, we should probably do a little renaming. My
fault for not looking yesterday.
http://www.ibiblio.org/maven/apache-jaxme/jars/
!!!!!!!!!!
http://www.ibiblio.org/maven/apache-jaxme/jars/jaxme-incubation-0.2.jar
we should probably have it more simply be
http://www.ibiblio.org/maven/jaxme/jars/jaxme-0.2.jar
http://www.ibiblio.org/maven/jaxme/jars/jaxme-SNAPSHOT.jar
http://www.ibiblio.org/maven/jaxme/jars/jaxme-rt-0.2.jar
http://www.ibiblio.org/maven/jaxme/jars/jaxme-rt-SNAPSHOT.jar
http://www.ibiblio.org/maven/jaxme/jars/jaxme-api-0.2.jar
http://www.ibiblio.org/maven/jaxme/jars/jaxme-api-SNAPSHOT.jar
http://www.ibiblio.org/maven/jaxme/jars/jaxme-js-0.2.jar
http://www.ibiblio.org/maven/jaxme/jars/jaxme-js-SNAPSHOT.jar
http://www.ibiblio.org/maven/jaxme/jars/jaxme-pm-0.2.jar
http://www.ibiblio.org/maven/jaxme/jars/jaxme-pm-SNAPSHOT.jar
http://www.ibiblio.org/maven/jaxme/jars/jaxme-xs-0.2.jar
http://www.ibiblio.org/maven/jaxme/jars/jaxme-xs-SNAPSHOT.jar
-Mark
robert burrell donkin wrote:
> hi mark
>
> i can see the jaxme jars on apache but not in the maven repository on
> ibiblio. is there anything else i need to do to push the content over
> there?
>
> (or have i just make some mistake in the upload...)
>
> - robert
>
> On 8 Mar 2004, at 22:20, Mark R. Diggory wrote:
>
>>
>>
>> robert burrell donkin wrote:
>>
>>> hi mark
>>> i've given it a go myself but i have a few questions and i'd
>>> appreciate it if you'd check my work so far.
>>> On 7 Mar 2004, at 16:18, Mark R. Diggory wrote:
>>>
>>>> You need to establish what your groups id will be. The current
>>>> naming trend for Apache "xml" projects has been a bit haphazard.
>>>>
>>>> xercies
>>>> xml-security
>>>> xml-resolver
>>>> xalan
>>>>
>>>> Some standardization here would be good. But that will not effect
>>>> maven.
>>>
>>> i've had a chat on IRC and gone for apache-jaxme
>>>
>>>> There is currently a problem with Maven publishing to a BSD system
>>>> and md5 signature generation, if you do not want to use maven to do
>>>> the publishing then these are the tasks you need to complete:
>>>>
>>>> 1.) The easiest way right now is for you to place the jars into
>>>>
>>>> java-repository/xml-jaxme/jars/...
>>>
>>> gone (but apache-jaxme rather than xml-jaxme)
>>>
>>>> 2.) Generate an md5 signature for each one in the same directory.
>>>> For instance as an examples
>>>>
>>>> "md5 xml-jaxme-1.0.jar > xml-jaxme-1.0.jar.md5" will produce:
>>>>
>>>> java-repository/xml-jaxme/jars/xml-jaxme-1.0.jar
>>>> java-repository/xml-jaxme/jars/xml-jaxme-1.0.jar.md5
>>>
>>> done
>>>
>>>> 3.) Generate the following symlinks the above files from
>>>>
>>>> java-repository/xml-jaxme/jars/xml-jaxme-SNAPSHOT.jar
>>>> java-repository/xml-jaxme/jars/xml-jaxme-SNAPSHOT.jar.md5
>>>
>>> done
>>>
>>>> 4.) and create a file
>>>>
>>>> java-repository/xml-jaxme/jars/xml-jaxme-snapshot-version with the
>>>> contents "1.0"
>>>
>>> these releases are versioned 0.2: should this file contain 0.2 (since
>>> it refers to the version of the jars) or 1.0 (since it's a mavenesque
>>> version number)
>>
>>
>> It would be wise, so yes, apache-jaxme-0.2.jar
>>
>>>> 5.) use the following "POM" in the
>>>>
>>>> java-repository/xml-jaxme/poms/project/pom
>>>> <project>
>>>> <pomVersion>3</pomVersion>
>>>> <id>xml-jaxme</id>
>>>> <name>xml-jaxme</name>
>>>> <currentVersion>1.0</currentVersion>
>>>> <organization>
>>>> <name>Apache Software Foundation</name>
>>>> <url>www.apache.org</url>
>>>> </organization>
>>>> <licenses>
>>>> <license>
>>>> <name>ASL 2.0</name>
>>>> <url>???????</url>
>>>> <comments>???????</comments>
>>>> </license>
>>>> </licenses>
>>>> </project>
>>>
>>> there are a number of jar in the release. i'd been working on the
>>> theory that each needs a separate artifact id. what should the
>>> contents of the file be in this case?
>>> - robert
>>
>>
>> Yes, it should look like:
>>
>> /java-repository/apache-jaxme/jars/<artifact>-<version>.jar
>>
>> /java-repository/apache-jaxme/poms/project/pom
>>
>> <project>
>> <pomVersion>3</pomVersion>
>> <groupId>apache-jaxme</groupId>
>> <name>Apache Jaxme</name>
>> <currentVersion>0.2</currentVersion>
>> <organization>
>> <name>Apache Software Foundation</name>
>> <url>www.apache.org</url>
>> </organization>
>> <licenses>
>> <license>
>> <name>ASL 2.0</name>
>> <url>http://www.apache.org/licenses/LICENSE-2.0</url>
>> </license>
>> </licenses>
>> </project>
>>
>> sound good, I'll take a look in the directory and verify all looks well.
>>
>> --
>> Mark Diggory
>> Software Developer
>> Harvard MIT Data Center
>> http://www.hmdc.harvard.edu
>>
>
--
Mark Diggory
Software Developer
Harvard MIT Data Center
http://www.hmdc.harvard.edu
Re: adding jaxme jars
Posted by robert burrell donkin <rd...@apache.org>.
hi mark
i can see the jaxme jars on apache but not in the maven repository on
ibiblio. is there anything else i need to do to push the content over
there?
(or have i just make some mistake in the upload...)
- robert
On 8 Mar 2004, at 22:20, Mark R. Diggory wrote:
>
>
> robert burrell donkin wrote:
>
>> hi mark
>> i've given it a go myself but i have a few questions and i'd
>> appreciate it if you'd check my work so far.
>> On 7 Mar 2004, at 16:18, Mark R. Diggory wrote:
>>> You need to establish what your groups id will be. The current
>>> naming trend for Apache "xml" projects has been a bit haphazard.
>>>
>>> xercies
>>> xml-security
>>> xml-resolver
>>> xalan
>>>
>>> Some standardization here would be good. But that will not effect
>>> maven.
>> i've had a chat on IRC and gone for apache-jaxme
>>> There is currently a problem with Maven publishing to a BSD system
>>> and md5 signature generation, if you do not want to use maven to do
>>> the publishing then these are the tasks you need to complete:
>>>
>>> 1.) The easiest way right now is for you to place the jars into
>>>
>>> java-repository/xml-jaxme/jars/...
>> gone (but apache-jaxme rather than xml-jaxme)
>>> 2.) Generate an md5 signature for each one in the same directory.
>>> For instance as an examples
>>>
>>> "md5 xml-jaxme-1.0.jar > xml-jaxme-1.0.jar.md5" will produce:
>>>
>>> java-repository/xml-jaxme/jars/xml-jaxme-1.0.jar
>>> java-repository/xml-jaxme/jars/xml-jaxme-1.0.jar.md5
>> done
>>> 3.) Generate the following symlinks the above files from
>>>
>>> java-repository/xml-jaxme/jars/xml-jaxme-SNAPSHOT.jar
>>> java-repository/xml-jaxme/jars/xml-jaxme-SNAPSHOT.jar.md5
>> done
>>> 4.) and create a file
>>>
>>> java-repository/xml-jaxme/jars/xml-jaxme-snapshot-version with the
>>> contents "1.0"
>> these releases are versioned 0.2: should this file contain 0.2 (since
>> it refers to the version of the jars) or 1.0 (since it's a mavenesque
>> version number)
>
> It would be wise, so yes, apache-jaxme-0.2.jar
>
>>> 5.) use the following "POM" in the
>>>
>>> java-repository/xml-jaxme/poms/project/pom
>>> <project>
>>> <pomVersion>3</pomVersion>
>>> <id>xml-jaxme</id>
>>> <name>xml-jaxme</name>
>>> <currentVersion>1.0</currentVersion>
>>> <organization>
>>> <name>Apache Software Foundation</name>
>>> <url>www.apache.org</url>
>>> </organization>
>>> <licenses>
>>> <license>
>>> <name>ASL 2.0</name>
>>> <url>???????</url>
>>> <comments>???????</comments>
>>> </license>
>>> </licenses>
>>> </project>
>> there are a number of jar in the release. i'd been working on the
>> theory that each needs a separate artifact id. what should the
>> contents of the file be in this case?
>> - robert
>
> Yes, it should look like:
>
> /java-repository/apache-jaxme/jars/<artifact>-<version>.jar
>
> /java-repository/apache-jaxme/poms/project/pom
>
> <project>
> <pomVersion>3</pomVersion>
> <groupId>apache-jaxme</groupId>
> <name>Apache Jaxme</name>
> <currentVersion>0.2</currentVersion>
> <organization>
> <name>Apache Software Foundation</name>
> <url>www.apache.org</url>
> </organization>
> <licenses>
> <license>
> <name>ASL 2.0</name>
> <url>http://www.apache.org/licenses/LICENSE-2.0</url>
> </license>
> </licenses>
> </project>
>
> sound good, I'll take a look in the directory and verify all looks
> well.
>
> --
> Mark Diggory
> Software Developer
> Harvard MIT Data Center
> http://www.hmdc.harvard.edu
>
Re: adding jaxme jars
Posted by "Mark R. Diggory" <md...@latte.harvard.edu>.
Its ok, half the projects in Maven repository never deployed pom's so
its usage is somewhat "speculative" in the first place.
-Mark
Erik Abele wrote:
> On 08.03.2004, at 23:20, Mark R. Diggory wrote:
>
>> <project>
>> <pomVersion>3</pomVersion>
>> <groupId>apache-jaxme</groupId>
>> <name>Apache Jaxme</name>
>> <currentVersion>0.2</currentVersion>
>> <organization>
>> <name>Apache Software Foundation</name>
>
>
> The official name is 'The Apache Software Foundation', as incorporated
> within the State of Delaware. See
> http://apache.org/foundation/records/certificate.html.
>
>> <url>www.apache.org</url>
>> </organization>
>> <licenses>
>> <license>
>> <name>ASL 2.0</name>
>
>
> It's AL 2.0 not ASL 2.0 (Apache License not Apache Software License).
>
>> <url>http://www.apache.org/licenses/LICENSE-2.0</url>
>> </license>
>> </licenses>
>> </project>
>
>
> Perhaps a bit pedantic but... :-)
>
> Cheers,
> Erik
--
Mark Diggory
Software Developer
Harvard MIT Data Center
http://www.hmdc.harvard.edu
Re: adding jaxme jars
Posted by Erik Abele <er...@codefaktor.de>.
On 08.03.2004, at 23:20, Mark R. Diggory wrote:
> <project>
> <pomVersion>3</pomVersion>
> <groupId>apache-jaxme</groupId>
> <name>Apache Jaxme</name>
> <currentVersion>0.2</currentVersion>
> <organization>
> <name>Apache Software Foundation</name>
The official name is 'The Apache Software Foundation', as incorporated
within the State of Delaware. See
http://apache.org/foundation/records/certificate.html.
> <url>www.apache.org</url>
> </organization>
> <licenses>
> <license>
> <name>ASL 2.0</name>
It's AL 2.0 not ASL 2.0 (Apache License not Apache Software License).
> <url>http://www.apache.org/licenses/LICENSE-2.0</url>
> </license>
> </licenses>
> </project>
Perhaps a bit pedantic but... :-)
Cheers,
Erik
Re: adding jaxme jars
Posted by "Mark R. Diggory" <md...@latte.harvard.edu>.
robert burrell donkin wrote:
> hi mark
>
> i've given it a go myself but i have a few questions and i'd appreciate
> it if you'd check my work so far.
>
> On 7 Mar 2004, at 16:18, Mark R. Diggory wrote:
>
>> You need to establish what your groups id will be. The current naming
>> trend for Apache "xml" projects has been a bit haphazard.
>>
>> xercies
>> xml-security
>> xml-resolver
>> xalan
>>
>> Some standardization here would be good. But that will not effect maven.
>
>
> i've had a chat on IRC and gone for apache-jaxme
>
>> There is currently a problem with Maven publishing to a BSD system and
>> md5 signature generation, if you do not want to use maven to do the
>> publishing then these are the tasks you need to complete:
>>
>> 1.) The easiest way right now is for you to place the jars into
>>
>> java-repository/xml-jaxme/jars/...
>
>
> gone (but apache-jaxme rather than xml-jaxme)
>
>> 2.) Generate an md5 signature for each one in the same directory. For
>> instance as an examples
>>
>> "md5 xml-jaxme-1.0.jar > xml-jaxme-1.0.jar.md5" will produce:
>>
>> java-repository/xml-jaxme/jars/xml-jaxme-1.0.jar
>> java-repository/xml-jaxme/jars/xml-jaxme-1.0.jar.md5
>
>
> done
>
>> 3.) Generate the following symlinks the above files from
>>
>> java-repository/xml-jaxme/jars/xml-jaxme-SNAPSHOT.jar
>> java-repository/xml-jaxme/jars/xml-jaxme-SNAPSHOT.jar.md5
>
>
> done
>
>> 4.) and create a file
>>
>> java-repository/xml-jaxme/jars/xml-jaxme-snapshot-version with the
>> contents "1.0"
>
>
> these releases are versioned 0.2: should this file contain 0.2 (since it
> refers to the version of the jars) or 1.0 (since it's a mavenesque
> version number)
It would be wise, so yes, apache-jaxme-0.2.jar
>
>> 5.) use the following "POM" in the
>>
>> java-repository/xml-jaxme/poms/project/pom
>> <project>
>> <pomVersion>3</pomVersion>
>> <id>xml-jaxme</id>
>> <name>xml-jaxme</name>
>> <currentVersion>1.0</currentVersion>
>> <organization>
>> <name>Apache Software Foundation</name>
>> <url>www.apache.org</url>
>> </organization>
>> <licenses>
>> <license>
>> <name>ASL 2.0</name>
>> <url>???????</url>
>> <comments>???????</comments>
>> </license>
>> </licenses>
>> </project>
>
>
> there are a number of jar in the release. i'd been working on the theory
> that each needs a separate artifact id. what should the contents of the
> file be in this case?
>
> - robert
>
Yes, it should look like:
/java-repository/apache-jaxme/jars/<artifact>-<version>.jar
/java-repository/apache-jaxme/poms/project/pom
<project>
<pomVersion>3</pomVersion>
<groupId>apache-jaxme</groupId>
<name>Apache Jaxme</name>
<currentVersion>0.2</currentVersion>
<organization>
<name>Apache Software Foundation</name>
<url>www.apache.org</url>
</organization>
<licenses>
<license>
<name>ASL 2.0</name>
<url>http://www.apache.org/licenses/LICENSE-2.0</url>
</license>
</licenses>
</project>
sound good, I'll take a look in the directory and verify all looks well.
--
Mark Diggory
Software Developer
Harvard MIT Data Center
http://www.hmdc.harvard.edu
Re: adding jaxme jars
Posted by robert burrell donkin <ro...@blueyonder.co.uk>.
hi mark
i've given it a go myself but i have a few questions and i'd appreciate
it if you'd check my work so far.
On 7 Mar 2004, at 16:18, Mark R. Diggory wrote:
> You need to establish what your groups id will be. The current naming
> trend for Apache "xml" projects has been a bit haphazard.
>
> xercies
> xml-security
> xml-resolver
> xalan
>
> Some standardization here would be good. But that will not effect
> maven.
i've had a chat on IRC and gone for apache-jaxme
> There is currently a problem with Maven publishing to a BSD system and
> md5 signature generation, if you do not want to use maven to do the
> publishing then these are the tasks you need to complete:
>
> 1.) The easiest way right now is for you to place the jars into
>
> java-repository/xml-jaxme/jars/...
gone (but apache-jaxme rather than xml-jaxme)
> 2.) Generate an md5 signature for each one in the same directory. For
> instance as an examples
>
> "md5 xml-jaxme-1.0.jar > xml-jaxme-1.0.jar.md5" will produce:
>
> java-repository/xml-jaxme/jars/xml-jaxme-1.0.jar
> java-repository/xml-jaxme/jars/xml-jaxme-1.0.jar.md5
done
> 3.) Generate the following symlinks the above files from
>
> java-repository/xml-jaxme/jars/xml-jaxme-SNAPSHOT.jar
> java-repository/xml-jaxme/jars/xml-jaxme-SNAPSHOT.jar.md5
done
> 4.) and create a file
>
> java-repository/xml-jaxme/jars/xml-jaxme-snapshot-version with the
> contents "1.0"
these releases are versioned 0.2: should this file contain 0.2 (since
it refers to the version of the jars) or 1.0 (since it's a mavenesque
version number)
> 5.) use the following "POM" in the
>
> java-repository/xml-jaxme/poms/project/pom
> <project>
> <pomVersion>3</pomVersion>
> <id>xml-jaxme</id>
> <name>xml-jaxme</name>
> <currentVersion>1.0</currentVersion>
> <organization>
> <name>Apache Software Foundation</name>
> <url>www.apache.org</url>
> </organization>
> <licenses>
> <license>
> <name>ASL 2.0</name>
> <url>???????</url>
> <comments>???????</comments>
> </license>
> </licenses>
> </project>
there are a number of jar in the release. i'd been working on the
theory that each needs a separate artifact id. what should the contents
of the file be in this case?
- robert
Re: adding jaxme jars
Posted by "Mark R. Diggory" <md...@latte.harvard.edu>.
I can setup this if you point me at the jars, however, here are the
steps if you want to explore it yourself right now:
---
You need to establish what your groups id will be. The current naming
trend for Apache "xml" projects has been a bit haphazard.
xercies
xml-security
xml-resolver
xalan
Some standardization here would be good. But that will not effect maven.
There is currently a problem with Maven publishing to a BSD system and
md5 signature generation, if you do not want to use maven to do the
publishing then these are the tasks you need to complete:
1.) The easiest way right now is for you to place the jars into
java-repository/xml-jaxme/jars/...
2.) Generate an md5 signature for each one in the same directory. For
instance as an examples
"md5 xml-jaxme-1.0.jar > xml-jaxme-1.0.jar.md5" will produce:
java-repository/xml-jaxme/jars/xml-jaxme-1.0.jar
java-repository/xml-jaxme/jars/xml-jaxme-1.0.jar.md5
3.) Generate the following symlinks the above files from
java-repository/xml-jaxme/jars/xml-jaxme-SNAPSHOT.jar
java-repository/xml-jaxme/jars/xml-jaxme-SNAPSHOT.jar.md5
4.) and create a file
java-repository/xml-jaxme/jars/xml-jaxme-snapshot-version with the
contents "1.0"
5.) use the following "POM" in the
java-repository/xml-jaxme/poms/project/pom
<project>
<pomVersion>3</pomVersion>
<id>xml-jaxme</id>
<name>xml-jaxme</name>
<currentVersion>1.0</currentVersion>
<organization>
<name>Apache Software Foundation</name>
<url>www.apache.org</url>
</organization>
<licenses>
<license>
<name>ASL 2.0</name>
<url>???????</url>
<comments>???????</comments>
</license>
</licenses>
</project>
-Mark
robert burrell donkin wrote:
> (i don't think that the raw jars are distributed at the moment so
> symlinking is out of the question.)
>
> since it's a maven repository, are there any guidelines about the right
> way to put stuff into there?
>
> what about the artifact id/group id stuff?
>
> - robert
>
> On 6 Mar 2004, at 23:20, Sander Striker wrote:
>
>> On Sat, 2004-03-06 at 23:43, Mark R. Diggory wrote:
>>
>>> I don't think we're referring to it as the official "Apache Repository".
>>> It is a Maven repository located on www.apache.org
>>>
>>> /www/www.apache.org/dist/java-repository is the location to get things
>>> into maven (it is rsynced with the maven repository at ibiblio.
>>
>>
>> And, reminder, all the mirrors listed here:
>> http://www.apache.org/mirrors/
>>
>> If you have jaxme jars elsewhere in dist/, please consider symlinking.
>>
>> Sander
>>
>
--
Mark Diggory
Software Developer
Harvard MIT Data Center
http://www.hmdc.harvard.edu
Re: adding jaxme jars
Posted by robert burrell donkin <rd...@apache.org>.
(i don't think that the raw jars are distributed at the moment so
symlinking is out of the question.)
since it's a maven repository, are there any guidelines about the right
way to put stuff into there?
what about the artifact id/group id stuff?
- robert
On 6 Mar 2004, at 23:20, Sander Striker wrote:
> On Sat, 2004-03-06 at 23:43, Mark R. Diggory wrote:
>> I don't think we're referring to it as the official "Apache
>> Repository".
>> It is a Maven repository located on www.apache.org
>>
>> /www/www.apache.org/dist/java-repository is the location to get things
>> into maven (it is rsynced with the maven repository at ibiblio.
>
> And, reminder, all the mirrors listed here:
> http://www.apache.org/mirrors/
>
> If you have jaxme jars elsewhere in dist/, please consider symlinking.
>
> Sander
>
Re: adding jaxme jars
Posted by Sander Striker <st...@apache.org>.
On Sat, 2004-03-06 at 23:43, Mark R. Diggory wrote:
> I don't think we're referring to it as the official "Apache Repository".
> It is a Maven repository located on www.apache.org
>
> /www/www.apache.org/dist/java-repository is the location to get things
> into maven (it is rsynced with the maven repository at ibiblio.
And, reminder, all the mirrors listed here:
http://www.apache.org/mirrors/
If you have jaxme jars elsewhere in dist/, please consider symlinking.
Sander
Re: adding jaxme jars
Posted by "Mark R. Diggory" <md...@latte.harvard.edu>.
I don't think we're referring to it as the official "Apache Repository".
It is a Maven repository located on www.apache.org
/www/www.apache.org/dist/java-repository is the location to get things
into maven (it is rsynced with the maven repository at ibiblio.
-Mark
robert burrell donkin wrote:
> i have a jelly tag library that uses jaxme (the apache JAXB
> implementation currently under incubation) that i'd like to commit into
> jakarta-commons. AIUI the right way to make ASF jars available for use
> in mavenized builds is to upload them into the apache repository.
>
> is this correct and is there any documentation about the right way to do
> this?
>
> - robert
>
--
Mark Diggory
Software Developer
Harvard MIT Data Center
http://www.hmdc.harvard.edu