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 176989 - [68cat] Cannot edit build properties in maven project
Summary: [68cat] Cannot edit build properties in maven project
Status: RESOLVED FIXED
Alias: None
Product: projects
Classification: Unclassified
Component: Maven (show other bugs)
Version: 6.x
Hardware: PC Linux
: P3 normal with 2 votes (vote)
Assignee: Antonin Nebuzelsky
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-17 05:08 UTC by neilg
Modified: 2010-08-03 03:13 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Project that illustrates the problem (1.12 KB, application/octet-stream)
2009-11-19 05:43 UTC, neilg
Details

Note You need to log in before you can comment on or make changes to this bug.
Description neilg 2009-11-17 05:08:04 UTC
In a maven reactor project I open the properties and set the maven.test.skip=true property for the "Build project" action. When I build the project by pressing F11 the maven.test.skip option is not present on the command line. Also, when I reopen the properties that property has not been saved.

I am using a maven reactor project and I have specified a profile within that project as its configuration.

Without the ability to set build properties I cannot use the maven support.
Comment 1 Jaroslav Pospisil 2009-11-18 07:01:50 UTC
Can't reproduce with Win Vista and build 200911171401. Reporter,could you please confirm,that issue is still reproducible? There was many fixes added recently.
Comment 2 David Simonek 2009-11-18 08:11:09 UTC
I can't reproduce either on Linux with current dev build. Property is correctly written into nbactions.xml file in the same dir as pom.xml of the project.

Reporter, please reopen if you still see the problem with detailed steps to reproduce, ideally also attached maven test project and with answers to following questions:
- what are "reactor projects"? Do you mean multi-module maven projects built with reactor plugin, with parent one with packaging "pom"?
- on which project did you define the property and pressed F11?
- can you be more specific about profile? Which profile in which project?
Thanks.
Comment 3 neilg 2009-11-19 05:42:44 UTC
This is still not working in 200911171401.

I'm attaching a demo project to illustrate the problem.

Steps to reproduce:
1. unarchive project
2. open the builder project in NB
3. right click on builder > set configuration > app
4. right click on builder > properties > actions > build project
5. add a=b property and click ok
6. right click on builder > properties > actions > build project (the a=b property will be there)
7. add c=d property and click ok
8. right click on builder > properties > actions > build project

Expected properties are:

a=b
c=d

actual properties are:

a=b
Comment 4 neilg 2009-11-19 05:43:41 UTC
Created attachment 91332 [details]
Project that illustrates the problem
Comment 5 Milos Kleint 2009-11-19 06:15:05 UTC
dafe?
Comment 6 neilg 2010-02-23 04:32:32 UTC
This defect makes using NB on complex maven projects almost impossible. At my current client we have a large multi-module project which requires multiple command line parameters and a profile to be set in order to build. Does anyone have a workaround?
Comment 7 jfeid 2010-05-14 08:08:09 UTC
I can confirm the issue in my system with the following details:

Product Version: NetBeans IDE 6.8 (Build 200912041610)
Java: 1.6.0_16; Java HotSpot(TM) Client VM 14.2-b01
System: Linux version 2.6.28-18-generic running on i386; UTF-8; en_US (nb)

I realized it when I tried to add a new property in an existing maven Action (Project Properties->Actions->Set Properties). It seems that this dialog ignores any property after the first line (keeps only the 1st line). The nbactions.xml & nbactions-dev.xml are not altered after save. 
Had to switch to command line for now. Is there is a workaround?
Comment 8 Antonin Nebuzelsky 2010-08-02 15:46:02 UTC
Confirming that subsequent edits of action's properties in a profile (configuration) are not saved. First edit of any action's properties in a profile are saved. Subsequent edits are not.

> Is there a workaround?

You can add the missing properties to nbactions-<profilename>.xml manually. To the same part of the file where properties from the first edit in UI were saved.
Comment 9 Antonin Nebuzelsky 2010-08-02 16:14:31 UTC
Fixed in trunk.

http://hg.netbeans.org/core-main/rev/23aea6693264
Comment 10 Quality Engineering 2010-08-03 03:13:11 UTC
Integrated into 'main-golden', will be available in build *201008030001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main/rev/23aea6693264
User: Antonin Nebuzelsky <anebuzelsky@netbeans.org>
Log: #176989: Cannot edit build properties in maven project.