-
1. Re: Tagging is not possible anymore because of Thirdparty
anil.saldhana Jul 12, 2007 8:22 PM (in response to bill.burke)Bill, that is my fault. I am still struggling with maven in various projects. I will fix it tonight. The upload happened in the afternoon today.
-
2. Re: Tagging is not possible anymore because of Thirdparty
anil.saldhana Jul 12, 2007 8:26 PM (in response to bill.burke)Can you tell me which jar change affected you? Can you paste an error here:
-
3. Re: Tagging is not possible anymore because of Thirdparty
anil.saldhana Jul 12, 2007 8:48 PM (in response to bill.burke)Bill, I have rolled back the addition of JASPI API into the JavaEE snapshot and uploaded the snapshot. Tell me if this fixes your build issue. If not, please post me an error.
-
4. Re: Tagging is not possible anymore because of Thirdparty
wolfc Jul 13, 2007 12:13 AM (in response to bill.burke)JASPI isn't part of JavaEE 5 and should not be in the JavaEE 5 snapshot.
I do not see the rollback. -
5. Re: Tagging is not possible anymore because of Thirdparty
anil.saldhana Jul 13, 2007 12:47 AM (in response to bill.burke)"wolfc" wrote:
JASPI isn't part of JavaEE 5 and should not be in the JavaEE 5 snapshot.
I do not see the rollback.
Scott has always wanted the api to be part of the ee snapshot/jar. -
6. Re: Tagging is not possible anymore because of Thirdparty
wolfc Jul 13, 2007 3:13 AM (in response to bill.burke)Is it in JavaEE 6?
Then it should be part of the JavaEE 6 snapshot.
Time to branch in that case. -
7. Re: Tagging is not possible anymore because of Thirdparty
bill.burke Jul 13, 2007 12:44 PM (in response to bill.burke)Anil, you're not the only one that commits snapshots. WE just either need to change the way we add snapshots to repository.jboss.org, or define a process as I mentioned above.
-
8. Re: Tagging is not possible anymore because of Thirdparty
pgier Jul 13, 2007 1:11 PM (in response to bill.burke)I think part of the problem currently is that releases can have snapshot dependencies. A snapshot build is meant to be temporary, so ideally each release is only dependent on other releases.
If you want to release a project that depends on a snapshot version of something, you should just ask for an alpha or beta release of that project. At least that way the next snapshot won't overwrite it.
After the switch to maven, this behaviour is enforced, and the snapshots will be more clearly separated by snapshots.jboss.org.