[#JRA-6693] Either use release versions of libraries - or post the src online

JIRA

Either use release versions of libraries - or post the src online

Created: 16/May/05 06:24 AM Updated: 01/Jun/05 06:14 PM

Component/s:

None

Affects Version/s:

3.2 Beta

Fix Version/s:

3.2

Time Tracking:

Not Specified

Participants:	Anton Mazkovoi [Atlassian], Brian Nguyen, Mark Chaimungkalanont [Atlassian] and Nick Minutello
Since last comment:	3 years, 12 weeks, 4 days ago
Resolution Date:	31/May/05 10:04 PM
Labels:

Description

« Hide

If we have to debug, we need the src... you cant bank on people being able to get it via cvs....

So far I notice:
ofbiz
osuser
statcvs

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Anton Mazkovoi [Atlassian] added a comment - 17/May/05 06:49 PM

Thanks for the note - we were planning to do this for 3.2 final.

[ Permlink | « Hide ]

Anton Mazkovoi [Atlassian] added a comment - 17/May/05 06:52 PM

Sorry, just to follow up on that:

We will definitely post up the source to packages that we patch. The packages which use a dated snapshot from their CVS can be checked out from their CVS repository and we prefer not to duplicate them on our repository. I know you are behind a firewall and we have talked about this before. Was using cvsgrab an option?

[ Permlink | « Hide ]

Nick Minutello added a comment - 17/May/05 06:53 PM

Excellent. Thanks.
(I noticed because I had to look at the ofbiz src...)

[ Permlink | « Hide ]

Nick Minutello added a comment - 17/May/05 08:05 PM

Responding to your second comment :

IIRC, you cant do a date-based cvsgrab checkout...
And cvsgrab isnt always a relieable option - in particular some CVS repos' arent accessible via viewcvs (e.g. java.net)

Not having ready access to the src for these "snapshot" based libraries has been a long-standing RPITA for us...
There have been a number of occasions where we have to chase down some production bug/problem with Jira or Confluence - and we cant match stack-trace line numbers with src....
To say its a PITA is an understatement.
And historically, when we have had this problem, its almost always been core libraries, like webwork or ofbiz or the like...

I am not suggesting that you keep this src in your own CVS - but when you check out the src to build these jars, it would take 20sec to zip up that same src and make it available for download.

[ Permlink | « Hide ]

Mark Chaimungkalanont [Atlassian] added a comment - 18/May/05 07:52 PM

Unless we're about to run out space on http://repository.atlassian.com, I don't really see a major problem with us running "maven jar:deploy dist:deploy-src" instead of "maven jar:deploy" when we build our snapshot libraries.

[ Permlink | « Hide ]

Nick Minutello added a comment - 18/May/05 09:58 PM

Mate, that would be ideal.
Any idea why http://repository.atlassian.com/ isnt browseable?
All I see is "repository.atlassian.com"

[ Permlink | « Hide ]

Mark Chaimungkalanont [Atlassian] added a comment - 19/May/05 12:33 AM

I think as a general rule, we didn't want people snooping around our repository. You'd only find stuff if you knew what you were looking for

[ Permlink | « Hide ]

Nick Minutello added a comment - 19/May/05 05:15 AM

Its a bit of a PITA though....

[ Permlink | « Hide ]

Anton Mazkovoi [Atlassian] added a comment - 31/May/05 10:04 PM

All the sources should be up there. Let us know if you have any problems with them.

[ Permlink | « Hide ]

Nick Minutello added a comment - 01/Jun/05 06:14 PM

Fantastic. Thanks.