-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ate Douma schrieb: > Carsten Ziegeler wrote: >> David H. DeWolf wrote: >>> The biggest question is probably concerning licensing and if we're >>> allowed to publish it. This may not be an issue, but it's >>> something we need to look into before we move forward. Yes this will be a problem, under this point of view this will be a big problem. So there won't be so many api changes, so we can let it as it is. >> Yepp, >> >> I'm not sure why we have to deploy this into a public available >> repository? Shouldn't the api be just a module which is build >> during the >> whole build as well? > I agree, this shouldn't be made available in a public repository yet > and I also don't see any technical reason why it should. > You really would need to get clearance from IBM for that. > >> >> For the version I guess '2.0-ED2-Rev13' is fine. > Yes, not SNAPSHOT for sure. > >> >> Carsten >>> [EMAIL PROTECTED] wrote: >>>> Hi all, >>>> >>>> As part of the development of the JSR-286 Reference >>>> Implementation, a copy of the portlet API jar (found here: >>>> http://ipc658.inf-swt.uni-jena.de/spec/JSR%202.0%20API/lib/) >>>> needs to be deployed to a Maven 2 repository. I was wondering >>>> which repository should I use for this purpose? Should it be the >>>> pluto-staging or apache.snapshot repository noted in the root >>>> pom.xml file or somewhere else? >>>> >>>> I also need to know what is the appropriate naming convention to >>>> use for this file (i.e. the version element in the pom.xml). The >>>> current portlet-2.0.jar is based on the Early Draft 2, Revision >>>> 13 of the JSR-286 spec, so it seems like the version element >>>> value should be something like '2.0-ED2-Rev13'. I'm not sure if >>>> we need to append 'SNAPSHOT' to this version value. Please advise? >>>> >>>> I am assuming that the groupId would be javax.portlet and the >>>> artifactId would be portlet-api for this file as is now the case >>>> for the portlet-1.0.jar file that contains the JSR-168 API. >>>> /Craig >> >> >
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGIJiDwaBuBD/AhYARAixbAKDMFEoifGfSKBXH5JR0XdGU98XRQwCfVdAs S96sUMHl1KjD/cAVXj8vwo4= =/QNZ -----END PGP SIGNATURE-----
