org.eclipse.wst.common.component deploy-name has version number?

View: New views
9 Messages — Rating Filter:   Alert me  

org.eclipse.wst.common.component deploy-name has version number?

by Shick, Trever :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Some parts of this message have been removed. Learn more about Nabble's security policy.

Can anyone shed light on why the deploy-name of the wb-module in org.eclipse.wst.common.component has a version number in it?

 

<?xml version="1.0" encoding="UTF-8"?>

<project-modules id="moduleCoreId" project-version="1.5.0">

      <wb-module deploy-name="my-webapp-1.0.0-SNAPSHOT">

      …

 

I’m using RAD 7.5 and the latest release m2Eclipse plugin with WebSphere 6.1.

 

What’s happening is that WebSphere 6.1 is pointing at a folder called ‘my-webapp’ (sans version #) but the folder in <workspace_root>\.metadata\.plugins\org.eclipse.wst.server.core\tmp0 has the version number.

 

I can only assume the folder name in tmp0\ is coming from the wb-module deploy-name.  I don’t know why the looseconfig.xmi  in .metadata\.plugins\com.ibm.etools.wrd.websphere\looseconfigurations\WebSphereApplicationServerv6.1atlocalhost is not using the version, but it seems to me like the deploy-name shouldn’t have the version anyhow. It should really just be the artifactId used for the ‘deploy-name’.

 

I think I see in the code where to change this, but I was hoping to get a little info on WHY the version number is used here before I patch it and use a custom version.

 

 

Trever M. Shick

 

 
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.

Re: org.eclipse.wst.common.component deploy-name has version number?

by Fred Bricon :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Trever,

this was done intentionally as per https://issues.sonatype.org/browse/MNGECLIPSE-965.

I started to work on ear modules configuration support a few months ago, so you could specifically use artifactId (or whatever) as the deploy name,
unfortunately, my hard drive crashed before I could check in my work in svn, and I never found the time to rework on it.

I plan on getting back at it in the next weeks, but I can't give a timeframe.

regards,

Fred Bricon


On Thu, May 28, 2009 at 8:46 PM, Shick, Trever <Trever.Shick@...> wrote:

Can anyone shed light on why the deploy-name of the wb-module in org.eclipse.wst.common.component has a version number in it?

 

<?xml version="1.0" encoding="UTF-8"?>

<project-modules id="moduleCoreId" project-version="1.5.0">

      <wb-module deploy-name="my-webapp-1.0.0-SNAPSHOT">

      …

 

I’m using RAD 7.5 and the latest release m2Eclipse plugin with WebSphere 6.1.

 

What’s happening is that WebSphere 6.1 is pointing at a folder called ‘my-webapp’ (sans version #) but the folder in <workspace_root>\.metadata\.plugins\org.eclipse.wst.server.core\tmp0 has the version number.

 

I can only assume the folder name in tmp0\ is coming from the wb-module deploy-name.  I don’t know why the looseconfig.xmi  in .metadata\.plugins\com.ibm.etools.wrd.websphere\looseconfigurations\WebSphereApplicationServerv6.1atlocalhost is not using the version, but it seems to me like the deploy-name shouldn’t have the version anyhow. It should really just be the artifactId used for the ‘deploy-name’.

 

I think I see in the code where to change this, but I was hoping to get a little info on WHY the version number is used here before I patch it and use a custom version.

 

 

Trever M. Shick

 

 
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.


Re: org.eclipse.wst.common.component deploy-name has version number?

by Eugene Kuleshov :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Trever,

Can you please check what is the project name in Eclipse and also show
maven-war-plugin configuration from your project pom.xml?

regards,
Eugene


Shick, Trever wrote:

>
> Can anyone shed light on why the deploy-name of the wb-module in
> org.eclipse.wst.common.component has a version number in it?
>
> <?xml version=/"1.0"/ encoding=/"UTF-8"/?>
>
> <project-modules id=/"moduleCoreId"/ project-version=/"1.5.0"/>
>
> <wb-module */deploy-name="my-webapp-1.0.0-SNAPSHOT">/*
>
> …
>
> I’m using RAD 7.5 and the latest release m2Eclipse plugin with
> WebSphere 6.1.
>
> What’s happening is that WebSphere 6.1 is pointing at a folder called
> ‘my-webapp’ (sans version #) but the folder in
> <workspace_root>\.metadata\.plugins\org.eclipse.wst.server.core\tmp0
> has the version number.
>
> I can only assume the folder name in tmp0\ is coming from the
> wb-module deploy-name. I don’t know why the looseconfig.xmi in
> .metadata\.plugins\com.ibm.etools.wrd.websphere\looseconfigurations\WebSphereApplicationServerv6.1atlocalhost
> is not using the version, but it seems to me like the deploy-name
> shouldn’t have the version anyhow. It should really just be the
> artifactId used for the ‘deploy-name’.
>
> I think I see in the code where to change this, but I was hoping to
> get a little info on WHY the version number is used here before I
> patch it and use a custom version.
>
> Trever M. Shick
>


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email



RE: org.eclipse.wst.common.component deploy-name has version number?

by Shick, Trever :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I have to look at a different project with the same issue. Sorry for the
'context switch'.

Here is the org.eclipse.wst.common.component file from my 'controlm'
maven nested module project.
The web module has a project name of 'controlm-webapp' (as you can see
below).  The deploy-name comes out with the version attached as you can
see in the deploy-name="controlm-webapp-0.0.1-SNAPSHOT".

<?xml version="1.0" encoding="UTF-8"?><project-modules id="moduleCoreId"
project-version="1.5.0">
        <wb-module deploy-name="controlm-webapp-0.0.1-SNAPSHOT">


<projectDescription>
        <name>controlm-webapp</name>



I have nothing specified in my configuration for the maven-war-plugin.
                <plugin>
                <artifactId>maven-war-plugin</artifactId>
                <version>2.0.2</version>
            </plugin>

At one point I did set the 'finalName' of the build configuration to NOT
use the version number but that didn't have any affect.



I think this would all be fixed if we had an output FileNameMapping type
of 'naked' or 'simple' that would just use the artifactId.









-----Original Message-----
From: Eugene Kuleshov [mailto:eu@...]
Sent: Thursday, May 28, 2009 3:55 PM
To: user@...
Subject: Re: [m2eclipse-user] org.eclipse.wst.common.component
deploy-name has version number?

Trever,

Can you please check what is the project name in Eclipse and also show
maven-war-plugin configuration from your project pom.xml?

regards,
Eugene


Shick, Trever wrote:

>
> Can anyone shed light on why the deploy-name of the wb-module in
> org.eclipse.wst.common.component has a version number in it?
>
> <?xml version=/"1.0"/ encoding=/"UTF-8"/?>
>
> <project-modules id=/"moduleCoreId"/ project-version=/"1.5.0"/>
>
> <wb-module */deploy-name="my-webapp-1.0.0-SNAPSHOT">/*
>
> ...
>
> I'm using RAD 7.5 and the latest release m2Eclipse plugin with
> WebSphere 6.1.
>
> What's happening is that WebSphere 6.1 is pointing at a folder called
> 'my-webapp' (sans version #) but the folder in
> <workspace_root>\.metadata\.plugins\org.eclipse.wst.server.core\tmp0
> has the version number.
>
> I can only assume the folder name in tmp0\ is coming from the
> wb-module deploy-name. I don't know why the looseconfig.xmi in
>
.metadata\.plugins\com.ibm.etools.wrd.websphere\looseconfigurations\WebS
phereApplicationServerv6.1atlocalhost

> is not using the version, but it seems to me like the deploy-name
> shouldn't have the version anyhow. It should really just be the
> artifactId used for the 'deploy-name'.
>
> I think I see in the code where to change this, but I was hoping to
> get a little info on WHY the version number is used here before I
> patch it and use a custom version.
>
> Trever M. Shick
>


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email



Re: org.eclipse.wst.common.component deploy-name has version number?

by daniel.green :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Did you ever solve this issue? It's driving me nuts!

Shick, Trever wrote:
Can anyone shed light on why the deploy-name of the wb-module in
org.eclipse.wst.common.component has a version number in it?

 

<?xml version="1.0" encoding="UTF-8"?>

<project-modules id="moduleCoreId" project-version="1.5.0">

      <wb-module deploy-name="my-webapp-1.0.0-SNAPSHOT">

      ...

 

I'm using RAD 7.5 and the latest release m2Eclipse plugin with WebSphere
6.1.

 

What's happening is that WebSphere 6.1 is pointing at a folder called
'my-webapp' (sans version #) but the folder in
<workspace_root>\.metadata\.plugins\org.eclipse.wst.server.core\tmp0 has
the version number.

 

I can only assume the folder name in tmp0\ is coming from the wb-module
deploy-name.  I don't know why the looseconfig.xmi  in
.metadata\.plugins\com.ibm.etools.wrd.websphere\looseconfigurations\WebS
phereApplicationServerv6.1atlocalhost is not using the version, but it
seems to me like the deploy-name shouldn't have the version anyhow. It
should really just be the artifactId used for the 'deploy-name'.

 

I think I see in the code where to change this, but I was hoping to get
a little info on WHY the version number is used here before I patch it
and use a custom version.

 

 

Trever M. Shick

 

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.

Re: org.eclipse.wst.common.component deploy-name has version number?

by Fred Bricon :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Daniel,

Have you tried the latest m2e 0.9.9 dev build (http://m2eclipse.sonatype.org/update-dev/)?
http://issues.sonatype.org/browse/MNGECLIPSE-1564 should be fixed, for workspace projects at least.

regards,

Fred Bricon

On Tue, Aug 25, 2009 at 7:36 PM, daniel.green <octoberdan@...> wrote:

Did you ever solve this issue? It's driving me nuts!


Shick, Trever wrote:
>
> Can anyone shed light on why the deploy-name of the wb-module in
> org.eclipse.wst.common.component has a version number in it?
>
>
>
> <?xml version="1.0" encoding="UTF-8"?>
>
> <project-modules id="moduleCoreId" project-version="1.5.0">
>
>       <wb-module deploy-name="my-webapp-1.0.0-SNAPSHOT">
>
>       ...
>
>
>
> I'm using RAD 7.5 and the latest release m2Eclipse plugin with WebSphere
> 6.1.
>
>
>
> What's happening is that WebSphere 6.1 is pointing at a folder called
> 'my-webapp' (sans version #) but the folder in
> <workspace_root>\.metadata\.plugins\org.eclipse.wst.server.core\tmp0 has
> the version number.
>
>
>
> I can only assume the folder name in tmp0\ is coming from the wb-module
> deploy-name.  I don't know why the looseconfig.xmi  in
> .metadata\.plugins\com.ibm.etools.wrd.websphere\looseconfigurations\WebS
> phereApplicationServerv6.1atlocalhost is not using the version, but it
> seems to me like the deploy-name shouldn't have the version anyhow. It
> should really just be the artifactId used for the 'deploy-name'.
>
>
>
> I think I see in the code where to change this, but I was hoping to get
> a little info on WHY the version number is used here before I patch it
> and use a custom version.
>
>
>
>
>
> Trever M. Shick
>
>
>
> This email and any files transmitted with it are confidential and intended
> solely for the use of the individual or entity to whom they are addressed.
> If you have received this email in error please notify the system manager.
> This message contains confidential information and is intended only for
> the individual named. If you are not the named addressee you should not
> disseminate, distribute or copy this e-mail.
>
>

--
View this message in context: http://www.nabble.com/org.eclipse.wst.common.component-deploy-name-has-version-number--tp23767685p25138879.html
Sent from the Maven Eclipse - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email




Re: org.eclipse.wst.common.component deploy-name has version number?

by sudhir_bhojwani :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi Fred,

I updated to 0.9.9, but the bug still exists. Can you please confirm it worked for you and what exact site did you use for downloading the plugin

thanks,
sudhir


Fred Bricon wrote:
Daniel,

Have you tried the latest m2e 0.9.9 dev build (
http://m2eclipse.sonatype.org/update-dev/)?
http://issues.sonatype.org/browse/MNGECLIPSE-1564 should be fixed, for
workspace projects at least.

regards,

Fred Bricon

On Tue, Aug 25, 2009 at 7:36 PM, daniel.green <octoberdan@gmail.com> wrote:

>
> Did you ever solve this issue? It's driving me nuts!
>
>
> Shick, Trever wrote:
> >
> > Can anyone shed light on why the deploy-name of the wb-module in
> > org.eclipse.wst.common.component has a version number in it?
> >
> >
> >
> > <?xml version="1.0" encoding="UTF-8"?>
> >
> > <project-modules id="moduleCoreId" project-version="1.5.0">
> >
> >       <wb-module deploy-name="my-webapp-1.0.0-SNAPSHOT">
> >
> >       ...
> >
> >
> >
> > I'm using RAD 7.5 and the latest release m2Eclipse plugin with WebSphere
> > 6.1.
> >
> >
> >
> > What's happening is that WebSphere 6.1 is pointing at a folder called
> > 'my-webapp' (sans version #) but the folder in
> > <workspace_root>\.metadata\.plugins\org.eclipse.wst.server.core\tmp0 has
> > the version number.
> >
> >
> >
> > I can only assume the folder name in tmp0\ is coming from the wb-module
> > deploy-name.  I don't know why the looseconfig.xmi  in
> > .metadata\.plugins\com.ibm.etools.wrd.websphere\looseconfigurations\WebS
> > phereApplicationServerv6.1atlocalhost is not using the version, but it
> > seems to me like the deploy-name shouldn't have the version anyhow. It
> > should really just be the artifactId used for the 'deploy-name'.
> >
> >
> >
> > I think I see in the code where to change this, but I was hoping to get
> > a little info on WHY the version number is used here before I patch it
> > and use a custom version.
> >
> >
> >
> >
> >
> > Trever M. Shick
> >
> >
> >
> > This email and any files transmitted with it are confidential and
> intended
> > solely for the use of the individual or entity to whom they are
> addressed.
> > If you have received this email in error please notify the system
> manager.
> > This message contains confidential information and is intended only for
> > the individual named. If you are not the named addressee you should not
> > disseminate, distribute or copy this e-mail.
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/org.eclipse.wst.common.component-deploy-name-has-version-number--tp23767685p25138879.html
> Sent from the Maven Eclipse - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>

Re: org.eclipse.wst.common.component deploy-name has version number?

by Fred Bricon :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I used the dev update site. Tested on Galileo / WTP 3.1.0. (Haven't tested Galileo SR1 / WTP 3.1.1 yet)

In fact there seem to be a problem when you set/change the bundleFileName of an existing web dependency. Updating the project configuration doesn't trigger the application.xml update for example, as it should.

If that's your case, try removing your web dependency and its settings from your ear's pom.xml, save the file, then add it back, configure its bundleFileName then save the file.

If you still can't see the changes, please open a JIRA issue (https://issues.sonatype.org/browse/MNGECLIPSE) . The more info you provide, the better (a test project, eclipse config, logs)

regards.

Fred Bricon

On Thu, Oct 15, 2009 at 8:34 PM, sudhir_bhojwani <sudhir.m.bhojwani2@...> wrote:

Hi Fred,

I updated to 0.9.9, but the bug still exists. Can you please confirm it
worked for you and what exact site did you use for downloading the plugin

thanks,
sudhir



Fred Bricon wrote:
>
> Daniel,
>
> Have you tried the latest m2e 0.9.9 dev build (
> http://m2eclipse.sonatype.org/update-dev/)?
> http://issues.sonatype.org/browse/MNGECLIPSE-1564 should be fixed, for
> workspace projects at least.
>
> regards,
>
> Fred Bricon
>
> On Tue, Aug 25, 2009 at 7:36 PM, daniel.green <octoberdan@...>
> wrote:
>
>>
>> Did you ever solve this issue? It's driving me nuts!
>>
>>
>> Shick, Trever wrote:
>> >
>> > Can anyone shed light on why the deploy-name of the wb-module in
>> > org.eclipse.wst.common.component has a version number in it?
>> >
>> >
>> >
>> > <?xml version="1.0" encoding="UTF-8"?>
>> >
>> > <project-modules id="moduleCoreId" project-version="1.5.0">
>> >
>> >       <wb-module deploy-name="my-webapp-1.0.0-SNAPSHOT">
>> >
>> >       ...
>> >
>> >
>> >
>> > I'm using RAD 7.5 and the latest release m2Eclipse plugin with
>> WebSphere
>> > 6.1.
>> >
>> >
>> >
>> > What's happening is that WebSphere 6.1 is pointing at a folder called
>> > 'my-webapp' (sans version #) but the folder in
>> > <workspace_root>\.metadata\.plugins\org.eclipse.wst.server.core\tmp0
>> has
>> > the version number.
>> >
>> >
>> >
>> > I can only assume the folder name in tmp0\ is coming from the wb-module
>> > deploy-name.  I don't know why the looseconfig.xmi  in
>> >
>> .metadata\.plugins\com.ibm.etools.wrd.websphere\looseconfigurations\WebS
>> > phereApplicationServerv6.1atlocalhost is not using the version, but it
>> > seems to me like the deploy-name shouldn't have the version anyhow. It
>> > should really just be the artifactId used for the 'deploy-name'.
>> >
>> >
>> >
>> > I think I see in the code where to change this, but I was hoping to get
>> > a little info on WHY the version number is used here before I patch it
>> > and use a custom version.
>> >
>> >
>> >
>> >
>> >
>> > Trever M. Shick
>> >
>> >
>> >
>> > This email and any files transmitted with it are confidential and
>> intended
>> > solely for the use of the individual or entity to whom they are
>> addressed.
>> > If you have received this email in error please notify the system
>> manager.
>> > This message contains confidential information and is intended only for
>> > the individual named. If you are not the named addressee you should not
>> > disseminate, distribute or copy this e-mail.
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/org.eclipse.wst.common.component-deploy-name-has-version-number--tp23767685p25138879.html
>> Sent from the Maven Eclipse - User mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>>
>
>

--
View this message in context: http://www.nabble.com/org.eclipse.wst.common.component-deploy-name-has-version-number--tp23767685p25913759.html
Sent from the Maven Eclipse - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email




Re: org.eclipse.wst.common.component deploy-name has version number?

by sudhir_bhojwani :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Thanks for a quick response. To unblock my team members, I added the version info to wst.component file. At least other can move forward. But that's not such a great solution when branching, and we do have multiple parallel branches. I will attach a sample project with details.

Thanks,
Sudhir


Fred Bricon wrote:
I used the dev update site. Tested on Galileo / WTP 3.1.0. (Haven't tested
Galileo SR1 / WTP 3.1.1 yet)

In fact there seem to be a problem when you set/change the bundleFileName of
an existing web dependency. Updating the project configuration doesn't
trigger the application.xml update for example, as it should.

If that's your case, try removing your web dependency and its settings from
your ear's pom.xml, save the file, then add it back, configure its
bundleFileName then save the file.

If you still can't see the changes, please open a JIRA issue (
https://issues.sonatype.org/browse/MNGECLIPSE) . The more info you provide,
the better (a test project, eclipse config, logs)

regards.

Fred Bricon

On Thu, Oct 15, 2009 at 8:34 PM, sudhir_bhojwani <
sudhir.m.bhojwani2@wellsfargo.com> wrote:

>
> Hi Fred,
>
> I updated to 0.9.9, but the bug still exists. Can you please confirm it
> worked for you and what exact site did you use for downloading the plugin
>
> thanks,
> sudhir
>
>
>
> Fred Bricon wrote:
> >
> > Daniel,
> >
> > Have you tried the latest m2e 0.9.9 dev build (
> > http://m2eclipse.sonatype.org/update-dev/)?
> > http://issues.sonatype.org/browse/MNGECLIPSE-1564 should be fixed, for
> > workspace projects at least.
> >
> > regards,
> >
> > Fred Bricon
> >
> > On Tue, Aug 25, 2009 at 7:36 PM, daniel.green <octoberdan@gmail.com>
> > wrote:
> >
> >>
> >> Did you ever solve this issue? It's driving me nuts!
> >>
> >>
> >> Shick, Trever wrote:
> >> >
> >> > Can anyone shed light on why the deploy-name of the wb-module in
> >> > org.eclipse.wst.common.component has a version number in it?
> >> >
> >> >
> >> >
> >> > <?xml version="1.0" encoding="UTF-8"?>
> >> >
> >> > <project-modules id="moduleCoreId" project-version="1.5.0">
> >> >
> >> >       <wb-module deploy-name="my-webapp-1.0.0-SNAPSHOT">
> >> >
> >> >       ...
> >> >
> >> >
> >> >
> >> > I'm using RAD 7.5 and the latest release m2Eclipse plugin with
> >> WebSphere
> >> > 6.1.
> >> >
> >> >
> >> >
> >> > What's happening is that WebSphere 6.1 is pointing at a folder called
> >> > 'my-webapp' (sans version #) but the folder in
> >> > <workspace_root>\.metadata\.plugins\org.eclipse.wst.server.core\tmp0
> >> has
> >> > the version number.
> >> >
> >> >
> >> >
> >> > I can only assume the folder name in tmp0\ is coming from the
> wb-module
> >> > deploy-name.  I don't know why the looseconfig.xmi  in
> >> >
> >> .metadata\.plugins\com.ibm.etools.wrd.websphere\looseconfigurations\WebS
> >> > phereApplicationServerv6.1atlocalhost is not using the version, but it
> >> > seems to me like the deploy-name shouldn't have the version anyhow. It
> >> > should really just be the artifactId used for the 'deploy-name'.
> >> >
> >> >
> >> >
> >> > I think I see in the code where to change this, but I was hoping to
> get
> >> > a little info on WHY the version number is used here before I patch it
> >> > and use a custom version.
> >> >
> >> >
> >> >
> >> >
> >> >
> >> > Trever M. Shick
> >> >
> >> >
> >> >
> >> > This email and any files transmitted with it are confidential and
> >> intended
> >> > solely for the use of the individual or entity to whom they are
> >> addressed.
> >> > If you have received this email in error please notify the system
> >> manager.
> >> > This message contains confidential information and is intended only
> for
> >> > the individual named. If you are not the named addressee you should
> not
> >> > disseminate, distribute or copy this e-mail.
> >> >
> >> >
> >>
> >> --
> >> View this message in context:
> >>
> http://www.nabble.com/org.eclipse.wst.common.component-deploy-name-has-version-number--tp23767685p25138879.html
> >> Sent from the Maven Eclipse - User mailing list archive at Nabble.com.
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe from this list, please visit:
> >>
> >>    http://xircles.codehaus.org/manage_email
> >>
> >>
> >>
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/org.eclipse.wst.common.component-deploy-name-has-version-number--tp23767685p25913759.html
> Sent from the Maven Eclipse - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>