This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 246293 - version number in the context path
Summary: version number in the context path
Status: RESOLVED WONTFIX
Alias: None
Product: serverplugins
Classification: Unclassified
Component: WildFly (show other bugs)
Version: 8.0
Hardware: PC Windows 8 x64
: P3 normal (vote)
Assignee: ehsavoie
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-06 08:52 UTC by cedrych
Modified: 2015-09-23 15:57 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description cedrych 2014-08-06 08:52:57 UTC
Hello,

When I create a Maven web application with WildFly in NetBeans the context path is initialized whith : "/mavenproject-1.0-SNAPSHOT".
When I run this project the "-1.0-SNAPSHOT" is in the url.
I prefer that the context path was initialzed without the version

WildFly plugin 1.0.17
NetBeans 8.0
WildFly 8.1.0

Regards,
Comment 1 ehsavoie 2014-08-06 08:57:05 UTC
You 'just' have to change that in the project properties to define the web context you want or change the artifact name in your pom.xml.
Comment 2 cedrych 2014-08-06 09:44:29 UTC
Thanks for your response.
But if most of people don't wan't the version in the context path* it's better to directly initialize context path without version so that we don't need to worry about.
It's not a defect but a proposal of enhancement. It's about ease of use.

*And I think it's the case, I never see version in url and GlassFish plugin behavior don't include version in the context path.
Comment 3 ehsavoie 2014-08-07 07:48:50 UTC
The problem is that this would require the creation of a jbossweb.xml which is not present in the maven archetype. 
This is something I tend to avoid as it is not what you would expect :
 - you are creating a foo-1.0-SNAPSHOT.war file (because the finalName is not defined in your pom)
 - you didn't specify something different in your project properties.

I don't like doing stuff not expected in a classic usage : if you did this using only Apache maven then you would get the same result which I think is fine.