[jboss-dev] why strip version from jarnames?

[Richard Opalka]

Hi Stan,

    unfortunately you didn't see what I was trying to say :(
I think I need to provide few examples to clarify my claims.

First example:

wsprovide.bat(.sh) shell script is distributed in a jar file
http://repository.jboss.org/maven2/org/jboss/ws/native/jbossws-native-resources/3.3.0.Beta2/jbossws-native-resources-3.3.0.Beta2.jar
that is part of JBossWS native release.
The content of this jar file is extracted to AS/bin directory during AS 
build phase.
It's not part of JBossAS code base, because this script (and also 
JBossWS product) is
intended to support multiple JBossAS versions, not just AS trunk.

Second example:

http://repository.jboss.org/maven2/org/jboss/ws/native/jbossws-native-client/3.3.0.Beta2/jbossws-native-client-3.3.0.Beta2.jar
file is also distributed as part of JBossWS native release.
This file contains !/META-INF/MANIFEST.MF/Class-Path entry
that defines client classpath.
So our users just need to put 
JBOSS_HOME/client/jbossws-native-client.jar to their classpath
and other necessary dependencies will be loaded by JVM using this 
manifest entry.

Both jar files have different lifecycle than JBossAS.
I know this is solvable problem, but
who would want to maintain it for versioned jars?
I'm not the volunteer :(

Rio

On 02/01/2010 03:53 PM, Stan Silvert wrote:
> Richard Opalka wrote:
>    
>> -1
>>
>> Using versioned jars in AS is road to maintainance hell IMHO :(
>> Note that there are some shell scripts in AS/bin
>> and many !/META-INF/MANIFEST.MF/Class-Path entries
>> in many jars referencing distribution jars.
>> And these scripts and jars usually have different lifecycle
>> (coming from different projects) than AS has.
>>
>> Rio
>>
>>      
> In general, I disagree.  NOT having the versioned jars makes things
> harder, especially for our users and support staff.
>
> We should be able to use Maven's filtering feature to automatically
> build the scripts with correct jar references, right?
>
>    
>> On 02/01/2010 04:42 AM, Paul Gier wrote:
>>
>>      
>>> When I switched the build to Maven I just kept the jars without versions because
>>> that's how it was before.  There are still a few places that refer to the
>>> specific jars names, but we can change this if we want.  As Adrian said, most of
>>> the testsuite jar references are created automatically, so it would only be an
>>> issue for the few that still refer directly to the name.
>>>
>>> Anil Saldhana wrote:
>>>
>>>
>>>        
>>>> Think there was a discussion on this 2 years ago. Cannot remember the reasons for the opposition
>>>> except that pre-maven builds/releases had no version names and we *maybe* decided to retain the process.
>>>>
>>>> One other reason may be that our build was not completely mavenized so all testsuite classpaths would
>>>> have to be updated with the version numbers in the jars.
>>>>
>>>>
>>>> On 01/29/2010 08:29 PM, Bill Burke wrote:
>>>>
>>>>
>>>>
>>>>          
>>>>> Just wondering, why strip version tags from jar names in jboss AS
>>>>> distribution?  Is this just practice or a requirement?
>>>>>
>>>>>
>>>>>
>>>>>            
>>>> _______________________________________________
>>>> jboss-development mailing list
>>>> jboss-development at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>>>
>>>>
>>>>          
>>> _______________________________________________
>>> jboss-development mailing list
>>> jboss-development at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>>
>>>
>>>        
>>
>>
>>      
>
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development
>    


-- 
Richard Opalka
ropalka at redhat.com
JBoss, by Red Hat

Office: +420 222 365 200
Mobile: +420 731 186 942