yes, you can, as these are only in m2.

I would like:
- to make the versions less complicated if we can.
- to get sanctioned, distributable versions of servlet/jsp api from the tomcat dev team

Carlos, could you do both of these?

Once this is done, can you update the page on the main web site (I'll get you access), and publish with:
maven -Dmaven.site.deploy.live=true site:deploy
A blog might be a good idea too.

Deprecation is a good idea. I had supersedes, but this is the opposite relatioship so should really have its own issue. Can you file it for beta-1?

Thanks,
Brett

Carlos Sanchez wrote:

I know, but if the author decides to use that version, what can we do?
for instance what do you suggest for the servlet api one? can't we use
2.4.public_draft as version?

On 6/20/05, John Casey <[EMAIL PROTECTED]> wrote:


the only thing I'd mention is that from a repository management
perspective it has been useful to parse the filename into it's
constituent parts (artifactId, classifier, version, type,
etc.)...'.public_draft' as a version-part will wreak havoc with this at
present.

It's along the same lines as the problems we've had with activemq and
geronimo in the m1->m2 conversion process...

-j

Carlos Sanchez wrote:

>Hi,

>I've uploaded m2 poms for some javax apis under javax.whatever groupIds
>http://www.ibiblio.org/maven2/javax/
>Related JIRA issue is http://jira.codehaus.org/browse/MEV-8

>So if you could take a look to groupIds, artifactIds, and so and vote
>if you agree.

>About the servlet api, I've checked the one bundled with tomcat 5.5
>and the version in the manifest is 2.4.public_draft, anyone knows if
>there's a final one and where to get it? I haven't found it under
>java.sun.com but seems there's a bunch of poms referencing servletapi
>2.4.

>and finally there's no deprecation information in the pom reference,
>is it already planned? should I create a JIRA issue?

>Regards

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




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



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





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

Reply via email to