Re: [EXT] Re: duplicate project netbeans error, how coud I do it?

[Luis tuti]

Many thanks for all your answers.
My requirements of copy project is for not make backup, is to createa a
new project in which I want to reuse  existing code  from an existing
project. For that reason is because I don't want use Git.

Thanks

El mar., 7 may. 2019 a las 0:14, Emilian Bold ()
escribió:

> @Thomas: I wasn't actually suggesting to remove the copy action. My
> impression is that this is a NetBeans bug (copy should work) or
> otherwise a minor UX bug (the action should be disabled if we can't
> manage).
>
> Of course the copy action is valuable. But since everybody was
> explaining how to copy *outside* NetBeans I was just half-questioning
> why we even have copy in there? We have it for a reason and it should
> work!
>
> --emi
>
> On Mon, May 6, 2019 at 11:08 PM Thomson, Duncan  wrote:
> >
> > I think the ability to copy projects within NetBeans is valuable, and
> should not be removed.  I use it, not for making backups, but for creating
> a new project in which I want to reuse some existing code or other stuff
> from an existing project.
> >
> >
> >
> > Duncan
> >
> >
> >
> > From: Emilian Bold 
> > Sent: Monday, May 6, 2019 1:27 PM
> > To: Thomson, Duncan 
> > Cc: Luis tuti ; Geertjan Wielenga <
> geert...@apache.org>; NetBeans Mailing 
> > Subject: Re: [EXT] Re: duplicate project netbeans error, how coud I do
> it?
> >
> >
> >
> > I think Luis figured out how to copy that folder but the question is why
> can't NetBeans figure that out?
> >
> >
> >
> > Our copy action could be disabled if there is something that we don't
> support anyhow.
> >
> >
> >
> > Or, we could get rid of the copy action entirely.
> >
> >
> >
> > The problem is one of NetBeans UX.
> >
> > --emi
> >
> >
> >
> > lun., 6 mai 2019, 19:21 Thomson, Duncan  a scris:
> >
> > I don’t know what it means for a project to have “external source
> roots”, but as others have noted, you have other (better) ways of making a
> backup of your code rather than using the Netbeans function to copy a
> project.
> >
> >
> >
> > Let me elaborate slightly.
> >
> >
> >
> > One way to do this is to use your operating system, outside of netbeans,
> to copy the directory structure.  I would recommend first exiting netbeans,
> just to make sure everything is actually written out to disk.  Then
> navigate to the directory containing the project and copy the entire
> directory structure.
> >
> >
> >
> > For example, on a Linux system your project might be
> /home/luistuti/NetBeansProjects/MostExcellentProject
> >
> >
> >
> > Then you would use something like:
> >
> >$ cp  –archive  MostExcellentProject  MostExcellentProject-copy
> >
> >
> >
> > Or create a tarball, using something like:
> >
> >   $ tar -cvzf MostExcellentProject.tgz MostExcellentProject
> >
> >
> >
> > But a much better way is to use a source code configuration control
> tool.  Nowadays everyone is using git, and it’s really powerful, so unless
> you already have a favorite that you want to use, I suggest you get on
> board with git.  Netbeans has very good integration with git, so you can do
> it from within Netbeans, or you can just go to the command line and run git
> commands from there.
> >
> >
> >
> > Good luck!
> >
> >
> >
> > Duncan
> >
> >
> >
> > From: Luis tuti 
> > Sent: Monday, May 6, 2019 6:36 AM
> > To: Emilian Bold 
> > Cc: Geertjan Wielenga ; NetBeans Mailing <
> users@netbeans.apache.org>
> > Subject: [EXT] Re: duplicate project netbeans error, how coud I do it?
> >
> >
> >
> > Yes, that's it.
> >
> >
> >
> > El lun., 6 may. 2019 a las 10:08, Emilian Bold ()
> escribió:
> >
> > Maybe this is the copy action from NetBeans?
> >
> > --emi
> >
> >
> >
> > lun., 6 mai 2019, 10:48 Geertjan Wielenga  a scris:
> >
> > You don't need NetBeans to copy a project, you can just go to your file
> system and copy it there.
> >
> >
> >
> > Gj
> >
> >
> >
> > On Mon, May 6, 2019 at 8:30 AM Luis tuti  wrote:
> >
> > Hi, I'm trying to copy a project to have a backup and mofiy my copy but
> I get: "The project has one more external source roots and cannot be copied"
> >
> > Someone could help me?
> >
> > Thanks
>

Sass comple error

[Peter Haworth]

Just getting started setting up Netbeans to compile sass files. Loaded the
sass compiler and set all the preferences including the one to compile on
save.. First time I try to compile, I get an error "Could not find an
option named "cache-location".  Any suggestions?
*Sent with Shift
*

Re: git partial commit

[Philip Durbin]

I believe this feature request is being tracked at
https://issues.apache.org/jira/browse/NETBEANS-428

On Mon, May 6, 2019 at 5:01 PM Mike Billman 
wrote:

> Is there a way to do this in netbeans?  Don’t have a current need, more
> just curious as we are moving from svn to git where I work.
>
>
>
> Mike Billman
>
> Senior Software Engineer
>
> CPTE
>
>
>
> [image: qclogo]
>
>
>
> 11800 Conrey Rd
>
> Suite 150
>
> Cincinnati, OH 45249
>
>
>
> T +1 513 469 1424
>
> E mikebill...@qcsoftware.com
>
> F +1 513 469 1425
>
>
>

Re: [EXT] Re: duplicate project netbeans error, how coud I do it?

[Emilian Bold]

@Thomas: I wasn't actually suggesting to remove the copy action. My
impression is that this is a NetBeans bug (copy should work) or
otherwise a minor UX bug (the action should be disabled if we can't
manage).

Of course the copy action is valuable. But since everybody was
explaining how to copy *outside* NetBeans I was just half-questioning
why we even have copy in there? We have it for a reason and it should
work!

--emi

On Mon, May 6, 2019 at 11:08 PM Thomson, Duncan  wrote:
>
> I think the ability to copy projects within NetBeans is valuable, and should 
> not be removed.  I use it, not for making backups, but for creating a new 
> project in which I want to reuse some existing code or other stuff from an 
> existing project.
>
>
>
> Duncan
>
>
>
> From: Emilian Bold 
> Sent: Monday, May 6, 2019 1:27 PM
> To: Thomson, Duncan 
> Cc: Luis tuti ; Geertjan Wielenga 
> ; NetBeans Mailing 
> Subject: Re: [EXT] Re: duplicate project netbeans error, how coud I do it?
>
>
>
> I think Luis figured out how to copy that folder but the question is why 
> can't NetBeans figure that out?
>
>
>
> Our copy action could be disabled if there is something that we don't support 
> anyhow.
>
>
>
> Or, we could get rid of the copy action entirely.
>
>
>
> The problem is one of NetBeans UX.
>
> --emi
>
>
>
> lun., 6 mai 2019, 19:21 Thomson, Duncan  a scris:
>
> I don’t know what it means for a project to have “external source roots”, but 
> as others have noted, you have other (better) ways of making a backup of your 
> code rather than using the Netbeans function to copy a project.
>
>
>
> Let me elaborate slightly.
>
>
>
> One way to do this is to use your operating system, outside of netbeans, to 
> copy the directory structure.  I would recommend first exiting netbeans, just 
> to make sure everything is actually written out to disk.  Then navigate to 
> the directory containing the project and copy the entire directory structure.
>
>
>
> For example, on a Linux system your project might be 
> /home/luistuti/NetBeansProjects/MostExcellentProject
>
>
>
> Then you would use something like:
>
>$ cp  –archive  MostExcellentProject  MostExcellentProject-copy
>
>
>
> Or create a tarball, using something like:
>
>   $ tar -cvzf MostExcellentProject.tgz MostExcellentProject
>
>
>
> But a much better way is to use a source code configuration control tool.  
> Nowadays everyone is using git, and it’s really powerful, so unless you 
> already have a favorite that you want to use, I suggest you get on board with 
> git.  Netbeans has very good integration with git, so you can do it from 
> within Netbeans, or you can just go to the command line and run git commands 
> from there.
>
>
>
> Good luck!
>
>
>
> Duncan
>
>
>
> From: Luis tuti 
> Sent: Monday, May 6, 2019 6:36 AM
> To: Emilian Bold 
> Cc: Geertjan Wielenga ; NetBeans Mailing 
> 
> Subject: [EXT] Re: duplicate project netbeans error, how coud I do it?
>
>
>
> Yes, that's it.
>
>
>
> El lun., 6 may. 2019 a las 10:08, Emilian Bold () 
> escribió:
>
> Maybe this is the copy action from NetBeans?
>
> --emi
>
>
>
> lun., 6 mai 2019, 10:48 Geertjan Wielenga  a scris:
>
> You don't need NetBeans to copy a project, you can just go to your file 
> system and copy it there.
>
>
>
> Gj
>
>
>
> On Mon, May 6, 2019 at 8:30 AM Luis tuti  wrote:
>
> Hi, I'm trying to copy a project to have a backup and mofiy my copy but I 
> get: "The project has one more external source roots and cannot be copied"
>
> Someone could help me?
>
> Thanks

-
To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
For additional commands, e-mail: users-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

git partial commit

[Mike Billman]

Is there a way to do this in netbeans?  Don't have a current need, more just 
curious as we are moving from svn to git where I work.

Mike Billman
Senior Software Engineer
CPTE

[qclogo]

11800 Conrey Rd
Suite 150
Cincinnati, OH 45249

T +1 513 469 1424
E mikebill...@qcsoftware.com
F +1 513 469 1425

Re: NB Platform Maven Dependencies

[arsi]

Hi,

And one more option...

|ClassLoader classLoader = 
Lookup.getDefault().lookup(ClassLoader.class);//get global classloader 
try { Class loadClass = 
classLoader.loadClass("org.netbeans.modules.settings.RecognizeInstanceObjects"); 
//access over java reflection } catch (ClassNotFoundException ex) { 
Exceptions.printStackTrace(ex); } |


​

ArSi

*From:* Arsi 
*Sent:* Monday, May 06, 2019 9:51PM
*To:* Users 
*Subject:* Re: NB Platform Maven Dependencies


Hi,

Each NB module has a defined list of public classes / packages, these 
are accessible to any other module:


|  
nbandroid.gradle.spi.* 
  |

​
eg: 
https://github.com/NBANDROIDTEAM/NBANDROID-V2/blob/78fb8c0d57ca98bcf462b7a66523d21976fd6a24/nbandroid.gradle.spi/pom.xml



All other classes are private and can only be accessed by friend modules.
You must define it in pom.xml as:

|org.netbeans.api:org-netbeans-modules-settings 
impl|

​
eg: 
https://github.com/NBANDROIDTEAM/NBANDROID-V2/blob/78fb8c0d57ca98bcf462b7a66523d21976fd6a24/nbandroid.core/pom.xml



This will link your module to the implementation version of the module 
you are compiling with.
If you try to install the module in NB that have a different 
implementation version of that module, you won't be able to install it..



I made a special installer and update server that can bypass it. But 
you must be sure that the definitions of the methods you use with 
those private classes have not changed in the newer version:


https://github.com/NBANDROIDTEAM/NBANDROID-V2-Autoupdate-plugin
https://github.com/NBANDROIDTEAM/NBANDROID-V2-Autoupdate-Web-server


And one more warning, NB Maven plugin sometimes tends to list this 
message if it can't find for example org.codehaus.jackson and that 
module is using it.
It is always necessary to read properly what is in the statement and 
not to automatically add impl dependency.


ArSi





*From:* Adam Korynta 
*Sent:* Monday, May 06, 2019 7:53PM
*To:* Netbeans Mailing List 
*Subject:* NB Platform Maven Dependencies


Hi All,

I’m trying to compile my Netbeans Platform modules using Maven, but 
I’m unable to compile due to the following errors:


[INFO] Private classes referenced in module: 
[org.netbeans.modules.settings.RecognizeInstanceObjects]


[ERROR] Project depends on packages not accessible at runtime in 
module org.netbeans.api:org-netbeans-modules-settings:nbm:RELEASE82


[INFO] Private classes referenced in module: 
[org.netbeans.modules.openide.util.ServiceProviderProcessor]


[ERROR] Project depends on packages not accessible at runtime in 
module org.netbeans.api:org-openide-util-lookup:nbm:RELEASE82


[INFO] Private classes referenced in module: 
[org.netbeans.modules.openide.filesystems.RecognizeInstanceFiles]


[ERROR] Project depends on packages not accessible at runtime in 
module org.netbeans.api:org-openide-filesystems:nbm:RELEASE82


These modules are declared in my pom.xml dependencies list as below:

<*dependency*><*groupId*>org.netbeans.api<*artifactId*>org-netbeans-modules-settings<*version*>${netbeans.version}<*type*>nbm<*dependency*><*groupId*>org.netbeans.api<*artifactId*>org-openide-util-lookup<*version*>${netbeans.version}<*type*>nbm<*dependency*><*groupId*>org.netbeans.api<*artifactId*>org-openide-filesystems<*version*>${netbeans.version}<*type*>nbm

When I look at the downloaded .jar and .nbm files, the MANIFEST.MFs’ 
OpenIDE-Module-Public-Packages entries do not contain the packages 
that are trying to be referenced. I’ve attached the 
org-netbeans-modules-settings-RELEASE82.jar’s MANIFEST.MF as an 
example. I would expect to find the “org.netbeans.modules.settings” 
package under the public packages listing.


If anyone could let me know what I’m doing wrong, that would be great1

Thank you,

Adam Korynta

/Resource Management Associates - Software Developer/

/1756 Picasso Avenue, Suite G, Davis, CA 95618/

/Phone 530-564-7043 ext. 217/

/Fax 530-231-5323/

/a...@rmanet.com/

/https://www.rmanet.com/

logo 


-
To unsubscribe, e-mail:users-unsubscr...@netbeans.apache.org
For additional commands, e-mail:users-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: NB Platform Maven Dependencies

[arsi]

Hi,

Each NB module has a defined list of public classes / packages, these 
are accessible to any other module:


|  
nbandroid.gradle.spi.*  
 |


​
eg: 
https://github.com/NBANDROIDTEAM/NBANDROID-V2/blob/78fb8c0d57ca98bcf462b7a66523d21976fd6a24/nbandroid.gradle.spi/pom.xml



All other classes are private and can only be accessed by friend modules.
You must define it in pom.xml as:

|org.netbeans.api:org-netbeans-modules-settings 
impl|


​
eg: 
https://github.com/NBANDROIDTEAM/NBANDROID-V2/blob/78fb8c0d57ca98bcf462b7a66523d21976fd6a24/nbandroid.core/pom.xml



This will link your module to the implementation version of the module 
you are compiling with.
If you try to install the module in NB that have a different 
implementation version of that module, you won't be able to install it..



I made a special installer and update server that can bypass it. But you 
must be sure that the definitions of the methods you use with those 
private classes have not changed in the newer version:


https://github.com/NBANDROIDTEAM/NBANDROID-V2-Autoupdate-plugin
https://github.com/NBANDROIDTEAM/NBANDROID-V2-Autoupdate-Web-server


And one more warning, NB Maven plugin sometimes tends to list this 
message if it can't find for example org.codehaus.jackson and that 
module is using it.
It is always necessary to read properly what is in the statement and not 
to automatically add impl dependency.


ArSi





*From:* Adam Korynta 
*Sent:* Monday, May 06, 2019 7:53PM
*To:* Netbeans Mailing List 
*Subject:* NB Platform Maven Dependencies


Hi All,

I’m trying to compile my Netbeans Platform modules using Maven, but 
I’m unable to compile due to the following errors:


[INFO] Private classes referenced in module: 
[org.netbeans.modules.settings.RecognizeInstanceObjects]


[ERROR] Project depends on packages not accessible at runtime in 
module org.netbeans.api:org-netbeans-modules-settings:nbm:RELEASE82


[INFO] Private classes referenced in module: 
[org.netbeans.modules.openide.util.ServiceProviderProcessor]


[ERROR] Project depends on packages not accessible at runtime in 
module org.netbeans.api:org-openide-util-lookup:nbm:RELEASE82


[INFO] Private classes referenced in module: 
[org.netbeans.modules.openide.filesystems.RecognizeInstanceFiles]


[ERROR] Project depends on packages not accessible at runtime in 
module org.netbeans.api:org-openide-filesystems:nbm:RELEASE82


These modules are declared in my pom.xml dependencies list as below:

<*dependency*><*groupId*>org.netbeans.api<*artifactId*>org-netbeans-modules-settings<*version*>${netbeans.version}<*type*>nbm<*dependency*><*groupId*>org.netbeans.api<*artifactId*>org-openide-util-lookup<*version*>${netbeans.version}<*type*>nbm<*dependency*><*groupId*>org.netbeans.api<*artifactId*>org-openide-filesystems<*version*>${netbeans.version}<*type*>nbm

When I look at the downloaded .jar and .nbm files, the MANIFEST.MFs’ 
OpenIDE-Module-Public-Packages entries do not contain the packages 
that are trying to be referenced. I’ve attached the 
org-netbeans-modules-settings-RELEASE82.jar’s MANIFEST.MF as an 
example. I would expect to find the “org.netbeans.modules.settings” 
package under the public packages listing.


If anyone could let me know what I’m doing wrong, that would be great1

Thank you,

Adam Korynta

/Resource Management Associates - Software Developer/

/1756 Picasso Avenue, Suite G, Davis, CA 95618/

/Phone 530-564-7043 ext. 217/

/Fax 530-231-5323/

/a...@rmanet.com/

/https://www.rmanet.com/

logo 


-
To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
For additional commands, e-mail: users-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

NB Platform Maven Dependencies

[Adam Korynta]

Hi All,

I'm trying to compile my Netbeans Platform modules using Maven, but I'm unable 
to compile due to the following errors:


[INFO] Private classes referenced in module: 
[org.netbeans.modules.settings.RecognizeInstanceObjects]
[ERROR] Project depends on packages not accessible at runtime in module 
org.netbeans.api:org-netbeans-modules-settings:nbm:RELEASE82
[INFO] Private classes referenced in module: 
[org.netbeans.modules.openide.util.ServiceProviderProcessor]
[ERROR] Project depends on packages not accessible at runtime in module 
org.netbeans.api:org-openide-util-lookup:nbm:RELEASE82
[INFO] Private classes referenced in module: 
[org.netbeans.modules.openide.filesystems.RecognizeInstanceFiles]
[ERROR] Project depends on packages not accessible at runtime in module 
org.netbeans.api:org-openide-filesystems:nbm:RELEASE82


These modules are declared in my pom.xml dependencies list as below:



   org.netbeans.api
   org-netbeans-modules-settings
   ${netbeans.version}
   nbm


   org.netbeans.api
   org-openide-util-lookup
   ${netbeans.version}
   nbm


   org.netbeans.api
   org-openide-filesystems
   ${netbeans.version}
   nbm


When I look at the downloaded .jar and .nbm files, the MANIFEST.MFs' 
OpenIDE-Module-Public-Packages entries do not contain the packages that are 
trying to be referenced. I've attached the 
org-netbeans-modules-settings-RELEASE82.jar's MANIFEST.MF as an example. I 
would expect to find the "org.netbeans.modules.settings" package under the 
public packages listing.

If anyone could let me know what I'm doing wrong, that would be great1

Thank you,

Adam Korynta
Resource Management Associates - Software Developer
1756 Picasso Avenue, Suite G, Davis, CA 95618
Phone 530-564-7043 ext. 217
Fax 530-231-5323
a...@rmanet.com
https://www.rmanet.com

[logo]



MANIFEST.MF
Description: MANIFEST.MF

-
To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
For additional commands, e-mail: users-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: NB Platform Maven Dependencies

[Emilian Bold]

I assume this is using Maven Central or the older NetBeans.org maven2
repository?

We recently published the Maven Central artefacts, it's possible there is a
bug...

--emi

lun., 6 mai 2019, 20:53 Adam Korynta  a scris:

> Hi All,
>
>
>
> I’m trying to compile my Netbeans Platform modules using Maven, but I’m
> unable to compile due to the following errors:
>
>
>
>
>
> [INFO] Private classes referenced in module:
> [org.netbeans.modules.settings.RecognizeInstanceObjects]
>
> [ERROR] Project depends on packages not accessible at runtime in module
> org.netbeans.api:org-netbeans-modules-settings:nbm:RELEASE82
>
> [INFO] Private classes referenced in module:
> [org.netbeans.modules.openide.util.ServiceProviderProcessor]
>
> [ERROR] Project depends on packages not accessible at runtime in module
> org.netbeans.api:org-openide-util-lookup:nbm:RELEASE82
>
> [INFO] Private classes referenced in module:
> [org.netbeans.modules.openide.filesystems.RecognizeInstanceFiles]
>
> [ERROR] Project depends on packages not accessible at runtime in module
> org.netbeans.api:org-openide-filesystems:nbm:RELEASE82
>
>
>
>
>
> These modules are declared in my pom.xml dependencies list as below:
>
>
>
>
> <*dependency*>
><*groupId*>org.netbeans.api
><*artifactId*>org-netbeans-modules-settings
><*version*>${netbeans.version}
><*type*>nbm
> 
> <*dependency*>
><*groupId*>org.netbeans.api
><*artifactId*>org-openide-util-lookup
><*version*>${netbeans.version}
><*type*>nbm
> 
> <*dependency*>
><*groupId*>org.netbeans.api
><*artifactId*>org-openide-filesystems
><*version*>${netbeans.version}
><*type*>nbm
> 
>
>
>
> When I look at the downloaded .jar and .nbm files, the MANIFEST.MFs’
> OpenIDE-Module-Public-Packages entries do not contain the packages that are
> trying to be referenced. I’ve attached the
> org-netbeans-modules-settings-RELEASE82.jar’s MANIFEST.MF as an example. I
> would expect to find the “org.netbeans.modules.settings” package under the
> public packages listing.
>
>
>
> If anyone could let me know what I’m doing wrong, that would be great1
>
>
>
> Thank you,
>
>
>
> Adam Korynta
>
> *Resource Management Associates - Software Developer*
>
> *1756 Picasso Avenue, Suite G, Davis, CA 95618*
>
> *Phone 530-564-7043 ext. 217*
>
> *Fax 530-231-5323*
>
> *a...@rmanet.com *
>
> *https://www.rmanet.com *
>
>
>
> [image: logo] 
>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
> For additional commands, e-mail: users-h...@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [EXT] Re: duplicate project netbeans error, how coud I do it?

[Emilian Bold]

I think Luis figured out how to copy that folder but the question is why
can't NetBeans figure that out?

Our copy action could be disabled if there is something that we don't
support anyhow.

Or, we could get rid of the copy action entirely.

The problem is one of NetBeans UX.

--emi

lun., 6 mai 2019, 19:21 Thomson, Duncan  a scris:

> I don’t know what it means for a project to have “external source roots”,
> but as others have noted, you have other (better) ways of making a backup
> of your code rather than using the Netbeans function to copy a project.
>
>
>
> Let me elaborate slightly.
>
>
>
> One way to do this is to use your operating system, outside of netbeans,
> to copy the directory structure.  I would recommend first exiting netbeans,
> just to make sure everything is actually written out to disk.  Then
> navigate to the directory containing the project and copy the entire
> directory structure.
>
>
>
> For example, on a Linux system your project might be
> /home/luistuti/NetBeansProjects/MostExcellentProject
>
>
>
> Then you would use something like:
>
>$ cp  –archive  MostExcellentProject  MostExcellentProject-copy
>
>
>
> Or create a tarball, using something like:
>
>   $ tar -cvzf MostExcellentProject.tgz MostExcellentProject
>
>
>
> But a much better way is to use a source code configuration control tool.
> Nowadays everyone is using git, and it’s really powerful, so unless you
> already have a favorite that you want to use, I suggest you get on board
> with git.  Netbeans has very good integration with git, so you can do it
> from within Netbeans, or you can just go to the command line and run git
> commands from there.
>
>
>
> Good luck!
>
>
>
> Duncan
>
>
>
> *From:* Luis tuti 
> *Sent:* Monday, May 6, 2019 6:36 AM
> *To:* Emilian Bold 
> *Cc:* Geertjan Wielenga ; NetBeans Mailing <
> users@netbeans.apache.org>
> *Subject:* [EXT] Re: duplicate project netbeans error, how coud I do it?
>
>
>
> Yes, that's it.
>
>
>
> El lun., 6 may. 2019 a las 10:08, Emilian Bold ()
> escribió:
>
> Maybe this is the copy action from NetBeans?
>
> --emi
>
>
>
> lun., 6 mai 2019, 10:48 Geertjan Wielenga  a scris:
>
> You don't need NetBeans to copy a project, you can just go to your file
> system and copy it there.
>
>
>
> Gj
>
>
>
> On Mon, May 6, 2019 at 8:30 AM Luis tuti  wrote:
>
> Hi, I'm trying to copy a project to have a backup and mofiy my copy but I
> get: "The project has one more external source roots and cannot be copied"
>
> Someone could help me?
>
> Thanks
>
>

Java 9+ is the module-info wizard too rigorous?

[Alten, Jessica-Aileen]

Hi,

I am quite new to the JDK 9+ module system but I think I found a bug in the
Netbeans module-info wizard (only tested with Netbeans 11). The problem is
the code generation for automatic modules, which seems too rigorous. In my
case, it is a maven project, but that does not matter, the Netbeans build
mechanism produces the same result.

Example: Using the jdom2-2.0.6.jar leads to this code

module mymodulename {
requires jdom;
}

Netbeans is fine with this, no errors, code completion works, but compiling
the code gives a compilation error:
... module not found: jdom

Changing "requires jdom" to "requires jdom2", in module-info.java results in
lots of red error badges in module-info.java and other classes, code
completion does not work and import statement says, "package org.jdom2.input
is declared in module jdom, but module mymodulename does not read it."

 But this works! Compilation is ok and the the class using the jdom2 package
is working fine!

Calling "jar --describe-module --file=jdom2-2.0.6.jar" gives:

jdom2@2.0.6 automatic
requires java.base mandated
contains org.jdom2
contains org.jdom2.adapters
contains org.jdom2.filter
contains org.jdom2.input
contains org.jdom2.input.sax
contains org.jdom2.input.stax
contains org.jdom2.internal
contains org.jdom2.located
contains org.jdom2.output
contains org.jdom2.output.support
contains org.jdom2.transform
contains org.jdom2.util
contains org.jdom2.xpath
contains org.jdom2.xpath.jaxen
contains org.jdom2.xpath.util

I read some articles about the module mechanism of JDK 9+ especially about
automatic modules and know that name generation for automatic modules
truncates the version string part, in this case that would be "-2.0.6" but
not "2-2.0.6", "2" is a distinctive feature not a version string. I think
the Netbeans wizard is doing too much here. Would you confirm this?

I know about the workarounds, i.e. modifying META-INF/MANIFEST.MF in the jar
file and I know that this library should be updated for JDK 9+, but I think
Netbeans should behave like the --describe-module result.
Or did I misunderstand something fundamentally?

Kind regards,
Jessica





smime.p7s
Description: S/MIME cryptographic signature

Re: duplicate project netbeans error, how coud I do it?

[Luis tuti]

Yes, that's it.

El lun., 6 may. 2019 a las 10:08, Emilian Bold ()
escribió:

> Maybe this is the copy action from NetBeans?
>
> --emi
>
> lun., 6 mai 2019, 10:48 Geertjan Wielenga  a scris:
>
>> You don't need NetBeans to copy a project, you can just go to your file
>> system and copy it there.
>>
>> Gj
>>
>> On Mon, May 6, 2019 at 8:30 AM Luis tuti  wrote:
>>
>>> Hi, I'm trying to copy a project to have a backup and mofiy my copy but
>>> I get: "The project has one more external source roots and cannot be copied"
>>>
>>> Someone could help me?
>>>
>>> Thanks
>>>
>>

Re: duplicate project netbeans error, how coud I do it?

[Emilian Bold]

Maybe this is the copy action from NetBeans?

--emi

lun., 6 mai 2019, 10:48 Geertjan Wielenga  a scris:

> You don't need NetBeans to copy a project, you can just go to your file
> system and copy it there.
>
> Gj
>
> On Mon, May 6, 2019 at 8:30 AM Luis tuti  wrote:
>
>> Hi, I'm trying to copy a project to have a backup and mofiy my copy but I
>> get: "The project has one more external source roots and cannot be copied"
>>
>> Someone could help me?
>>
>> Thanks
>>
>

Re: duplicate project netbeans error, how coud I do it?

[Geertjan Wielenga]

And also, use a versioning system and you won't need to make copies, e.g.,
check your code into GitHub.

Gj

On Mon, May 6, 2019 at 9:48 AM Geertjan Wielenga 
wrote:

> You don't need NetBeans to copy a project, you can just go to your file
> system and copy it there.
>
> Gj
>
> On Mon, May 6, 2019 at 8:30 AM Luis tuti  wrote:
>
>> Hi, I'm trying to copy a project to have a backup and mofiy my copy but I
>> get: "The project has one more external source roots and cannot be copied"
>>
>> Someone could help me?
>>
>> Thanks
>>
>

duplicate project netbeans error, how coud I do it?

[Luis tuti]

Hi, I'm trying to copy a project to have a backup and mofiy my copy but I
get: "The project has one more external source roots and cannot be copied"

Someone could help me?

Thanks