[jira] [Commented] (SYNCOPE-457) Must be able to configure JavaMailSender used by NotificationJob
[ https://issues.apache.org/jira/browse/SYNCOPE-457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13839004#comment-13839004 ] Hadrian Zbarcea commented on SYNCOPE-457: - Thanks Francisco. I like your changes. Simpler and cleaner. I had the impression that the community has a strong preference for properties defined via .properties file. Wiki updated, I have the necessary karma. > Must be able to configure JavaMailSender used by NotificationJob > > > Key: SYNCOPE-457 > URL: https://issues.apache.org/jira/browse/SYNCOPE-457 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 1.1.5, 1.2.0 >Reporter: Hadrian Zbarcea >Assignee: Hadrian Zbarcea > Fix For: 1.2.0 > > Attachments: syncope-457.patch > > > In NotificationJob.executeSingle we instantiate a new JavaMailSenderImpl() > which we then populate with some values. There are however other properties > [1] that can be set on the Session. Some of them are very useful, especially > in production environments. > In particular, the 'mail.smtp.connectiontimeout' should be set to a different > value than the default 'infinite' which would cause the thread to hang, > waiting for a unresponsive SMTP server (either misconfiguration of server > down). > I will try to come up with a patch towards the end of the week if nobody > beats me to it. > [1] https://javamail.java.net/nonav/docs/api/ -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (SYNCOPE-457) Must be able to configure JavaMailSender used by NotificationJob
[ https://issues.apache.org/jira/browse/SYNCOPE-457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13838663#comment-13838663 ] Hadrian Zbarcea commented on SYNCOPE-457: - Please find attached a patch implementing the solution suggested. As I suspected, there is a place where we need to override the mailSender, namely the NotificationTest. Since the fields are private and needed to override the mailSender, I could have added a public setter, but that was not very elegant. Overriding the mail.properties was not great either, because it was doing so for all the tests. I chose to add a mail-notification.properties, specific for that test and a new context defining just the property-placeholder (I prefer the xml syntax), but then I had to specify an order. I also removed the entries from content.xml. That's pretty much it. I hope it's complete, but I am not sure what (if anything) needs to be documented for a migration guide from the 1.1.x version to 1.2.0, in terms of configuration. I am also not sure if the changes in configuration have any impact on the console gui. > Must be able to configure JavaMailSender used by NotificationJob > > > Key: SYNCOPE-457 > URL: https://issues.apache.org/jira/browse/SYNCOPE-457 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 1.1.5, 1.2.0 >Reporter: Hadrian Zbarcea >Assignee: Hadrian Zbarcea > Fix For: 1.2.0 > > Attachments: syncope-457.patch > > > In NotificationJob.executeSingle we instantiate a new JavaMailSenderImpl() > which we then populate with some values. There are however other properties > [1] that can be set on the Session. Some of them are very useful, especially > in production environments. > In particular, the 'mail.smtp.connectiontimeout' should be set to a different > value than the default 'infinite' which would cause the thread to hang, > waiting for a unresponsive SMTP server (either misconfiguration of server > down). > I will try to come up with a patch towards the end of the week if nobody > beats me to it. > [1] https://javamail.java.net/nonav/docs/api/ -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (SYNCOPE-457) Must be able to configure JavaMailSender used by NotificationJob
[ https://issues.apache.org/jira/browse/SYNCOPE-457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hadrian Zbarcea updated SYNCOPE-457: Attachment: syncope-457.patch > Must be able to configure JavaMailSender used by NotificationJob > > > Key: SYNCOPE-457 > URL: https://issues.apache.org/jira/browse/SYNCOPE-457 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 1.1.5, 1.2.0 >Reporter: Hadrian Zbarcea >Assignee: Hadrian Zbarcea > Fix For: 1.2.0 > > Attachments: syncope-457.patch > > > In NotificationJob.executeSingle we instantiate a new JavaMailSenderImpl() > which we then populate with some values. There are however other properties > [1] that can be set on the Session. Some of them are very useful, especially > in production environments. > In particular, the 'mail.smtp.connectiontimeout' should be set to a different > value than the default 'infinite' which would cause the thread to hang, > waiting for a unresponsive SMTP server (either misconfiguration of server > down). > I will try to come up with a patch towards the end of the week if nobody > beats me to it. > [1] https://javamail.java.net/nonav/docs/api/ -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (SYNCOPE-457) Must be able to configure JavaMailSender used by NotificationJob
[ https://issues.apache.org/jira/browse/SYNCOPE-457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13837633#comment-13837633 ] Hadrian Zbarcea commented on SYNCOPE-457: - I was thinking about something along the same lines. It has the added advantage of not creating a new JavaMailSenderImpl instance for every send. What I am not yet sure about is if we need to have an SMTP host per sender. Can we have multiple/different senders? Still a noob on syncope :). > Must be able to configure JavaMailSender used by NotificationJob > > > Key: SYNCOPE-457 > URL: https://issues.apache.org/jira/browse/SYNCOPE-457 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 1.1.5, 1.2.0 >Reporter: Hadrian Zbarcea >Assignee: Hadrian Zbarcea > Fix For: 1.2.0 > > > In NotificationJob.executeSingle we instantiate a new JavaMailSenderImpl() > which we then populate with some values. There are however other properties > [1] that can be set on the Session. Some of them are very useful, especially > in production environments. > In particular, the 'mail.smtp.connectiontimeout' should be set to a different > value than the default 'infinite' which would cause the thread to hang, > waiting for a unresponsive SMTP server (either misconfiguration of server > down). > I will try to come up with a patch towards the end of the week if nobody > beats me to it. > [1] https://javamail.java.net/nonav/docs/api/ -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (SYNCOPE-456) TaskTestITCase failures
[ https://issues.apache.org/jira/browse/SYNCOPE-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hadrian Zbarcea resolved SYNCOPE-456. - Resolution: Fixed > TaskTestITCase failures > --- > > Key: SYNCOPE-456 > URL: https://issues.apache.org/jira/browse/SYNCOPE-456 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 1.2.0 >Reporter: Hadrian Zbarcea >Assignee: Hadrian Zbarcea > Attachments: syncope-456.patch > > > Both issueSYNCOPE81 and issueSYNCOPE86 fail on my system. The symptom is that > TaskController.execute hangs (the line below is the last in the log) and then > there is a timeout on the client side. > 22:46:09.087 DEBUG org.apache.syncope.core.rest.controller.ControllerHandler > - Before TaskController.execute([101, false]) > I am not sure if anybody saw this, if so please add a comment. I reproduce > the issue consistently on my Ubuntu laptop with both sun and openjdk 6. > Others don't see it in an environment similar to mine. I also saw it on a > CentOS server. I cannot reproduce it on osx though. It is quite likely > related to the environment, but nevertheless syncope should be more robust > and handle errors gracefully in a misconfigured environment. > Since I have environments that both work and don't, I will try to dig deeper, > compare the two and see what the culprit is. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (SYNCOPE-456) TaskTestITCase failures
[ https://issues.apache.org/jira/browse/SYNCOPE-456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13837631#comment-13837631 ] Hadrian Zbarcea commented on SYNCOPE-456: - Hmm, but with a valid fqdn I have the same issue :(. Let me dig into this a bit more. There may be some other configuration needed. For now, I think best is to leave this as is (as the tests pass), and I'll put a better fix with SYNCOPE-457. Is that ok? > TaskTestITCase failures > --- > > Key: SYNCOPE-456 > URL: https://issues.apache.org/jira/browse/SYNCOPE-456 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 1.2.0 >Reporter: Hadrian Zbarcea >Assignee: Hadrian Zbarcea > Attachments: syncope-456.patch > > > Both issueSYNCOPE81 and issueSYNCOPE86 fail on my system. The symptom is that > TaskController.execute hangs (the line below is the last in the log) and then > there is a timeout on the client side. > 22:46:09.087 DEBUG org.apache.syncope.core.rest.controller.ControllerHandler > - Before TaskController.execute([101, false]) > I am not sure if anybody saw this, if so please add a comment. I reproduce > the issue consistently on my Ubuntu laptop with both sun and openjdk 6. > Others don't see it in an environment similar to mine. I also saw it on a > CentOS server. I cannot reproduce it on osx though. It is quite likely > related to the environment, but nevertheless syncope should be more robust > and handle errors gracefully in a misconfigured environment. > Since I have environments that both work and don't, I will try to dig deeper, > compare the two and see what the culprit is. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Reopened] (SYNCOPE-456) TaskTestITCase failures
[
https://issues.apache.org/jira/browse/SYNCOPE-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hadrian Zbarcea reopened SYNCOPE-456:
-
Sorry, I had a temporary brain freeze. In core/src/test/resources/content.xml,
he hostname should be "not-existing.syncope.apache.org" not not-existing@s.a.o
('dot' instead of '@'). It does work but it's not quite a correct fqdn :).
Doh...
> TaskTestITCase failures
> ---
>
> Key: SYNCOPE-456
> URL: https://issues.apache.org/jira/browse/SYNCOPE-456
> Project: Syncope
> Issue Type: Bug
> Components: core
>Affects Versions: 1.2.0
>Reporter: Hadrian Zbarcea
>Assignee: Hadrian Zbarcea
> Attachments: syncope-456.patch
>
>
> Both issueSYNCOPE81 and issueSYNCOPE86 fail on my system. The symptom is that
> TaskController.execute hangs (the line below is the last in the log) and then
> there is a timeout on the client side.
> 22:46:09.087 DEBUG org.apache.syncope.core.rest.controller.ControllerHandler
> - Before TaskController.execute([101, false])
> I am not sure if anybody saw this, if so please add a comment. I reproduce
> the issue consistently on my Ubuntu laptop with both sun and openjdk 6.
> Others don't see it in an environment similar to mine. I also saw it on a
> CentOS server. I cannot reproduce it on osx though. It is quite likely
> related to the environment, but nevertheless syncope should be more robust
> and handle errors gracefully in a misconfigured environment.
> Since I have environments that both work and don't, I will try to dig deeper,
> compare the two and see what the culprit is.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (SYNCOPE-456) TaskTestITCase failures
[ https://issues.apache.org/jira/browse/SYNCOPE-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hadrian Zbarcea updated SYNCOPE-456: Attachment: syncope-456.patch > TaskTestITCase failures > --- > > Key: SYNCOPE-456 > URL: https://issues.apache.org/jira/browse/SYNCOPE-456 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 1.2.0 >Reporter: Hadrian Zbarcea >Assignee: Hadrian Zbarcea > Attachments: syncope-456.patch > > > Both issueSYNCOPE81 and issueSYNCOPE86 fail on my system. The symptom is that > TaskController.execute hangs (the line below is the last in the log) and then > there is a timeout on the client side. > 22:46:09.087 DEBUG org.apache.syncope.core.rest.controller.ControllerHandler > - Before TaskController.execute([101, false]) > I am not sure if anybody saw this, if so please add a comment. I reproduce > the issue consistently on my Ubuntu laptop with both sun and openjdk 6. > Others don't see it in an environment similar to mine. I also saw it on a > CentOS server. I cannot reproduce it on osx though. It is quite likely > related to the environment, but nevertheless syncope should be more robust > and handle errors gracefully in a misconfigured environment. > Since I have environments that both work and don't, I will try to dig deeper, > compare the two and see what the culprit is. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (SYNCOPE-456) TaskTestITCase failures
[
https://issues.apache.org/jira/browse/SYNCOPE-456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13837254#comment-13837254
]
Hadrian Zbarcea commented on SYNCOPE-456:
-
Mystery solved. I suspect other devs in the US might have experienced the same
thing. My isp is verizon (fios) and I get a dynamic ip and inherit the dns
servers configured by the isp. I do not define my own. Verizon has a 'feature'
in the dns server where, if you query for a non-fqdn host it actually resolves
it to one of its own dns search servers. As such, on my system, I was never
getting the {{java.net.UnknownHostException: not-existing}} because the dns was
resolving the "non-existing" host to 199.101.28.20 (which is actually
http://search.dnsassist.verizon.net/).
{code}
hadrian@rem:syncope$ nslookup non-existing
Server: 127.0.1.1
Address:127.0.1.1#53
Non-authoritative answer:
Name: non-existing
Address: 199.101.28.20
{code}
Next syncope attempted to connect to the (assumed to be an smtp) server. Due to
the default configuration (see SYNCOPE-457) the result was an infinite wait and
hence a hang in that thread.
Using an FQDN for the 'non-existing' host makes the dns behave as expected and
solves the test problem. See patch. Patch contains some extra entries in
.gitignore to ignore eclipse generated artifacts.
> TaskTestITCase failures
> ---
>
> Key: SYNCOPE-456
> URL: https://issues.apache.org/jira/browse/SYNCOPE-456
> Project: Syncope
> Issue Type: Bug
> Components: core
>Affects Versions: 1.2.0
>Reporter: Hadrian Zbarcea
>Assignee: Hadrian Zbarcea
> Attachments: syncope-456.patch
>
>
> Both issueSYNCOPE81 and issueSYNCOPE86 fail on my system. The symptom is that
> TaskController.execute hangs (the line below is the last in the log) and then
> there is a timeout on the client side.
> 22:46:09.087 DEBUG org.apache.syncope.core.rest.controller.ControllerHandler
> - Before TaskController.execute([101, false])
> I am not sure if anybody saw this, if so please add a comment. I reproduce
> the issue consistently on my Ubuntu laptop with both sun and openjdk 6.
> Others don't see it in an environment similar to mine. I also saw it on a
> CentOS server. I cannot reproduce it on osx though. It is quite likely
> related to the environment, but nevertheless syncope should be more robust
> and handle errors gracefully in a misconfigured environment.
> Since I have environments that both work and don't, I will try to dig deeper,
> compare the two and see what the culprit is.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Created] (SYNCOPE-457) Must be able to configure JavaMailSender used by NotificationJob
Hadrian Zbarcea created SYNCOPE-457: --- Summary: Must be able to configure JavaMailSender used by NotificationJob Key: SYNCOPE-457 URL: https://issues.apache.org/jira/browse/SYNCOPE-457 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.1.5, 1.2.0 Reporter: Hadrian Zbarcea Assignee: Hadrian Zbarcea In NotificationJob.executeSingle we instantiate a new JavaMailSenderImpl() which we then populate with some values. There are however other properties [1] that can be set on the Session. Some of them are very useful, especially in production environments. In particular, the 'mail.smtp.connectiontimeout' should be set to a different value than the default 'infinite' which would cause the thread to hang, waiting for a unresponsive SMTP server (either misconfiguration of server down). I will try to come up with a patch towards the end of the week if nobody beats me to it. [1] https://javamail.java.net/nonav/docs/api/ -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (SYNCOPE-456) TaskTestITCase failures
[
https://issues.apache.org/jira/browse/SYNCOPE-456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1383#comment-1383
]
Hadrian Zbarcea commented on SYNCOPE-456:
-
The failing process hangs before the following snippet (take from an
environment where the tests pass). The issue seems related with the host lookup
or other network configuration. Will try to figure out the exact line.
{code}
22:48:25.304 DEBUG org.apache.syncope.core.rest.controller.ControllerHandler -
After returning TaskController.execute:
org.apache.syncope.common.to.TaskExecTO@40c6e398[
task=101
id=10
status=NOT_SENT
message=MailSendException: Mail server connection failed; nested exception is
javax.mail.MessagingException: Connection error (java.net.UnknownHostException:
not-existing). Failed messages: javax.mail.MessagingException: Connection error
(java.net.UnknownHostException: not-existing)
org.springframework.mail.MailSendException: Mail server connection failed;
nested exception is javax.mail.MessagingException: Connection error
(java.net.UnknownHostException: not-existing). Failed messages:
javax.mail.MessagingException: Connection error (java.net.UnknownHostException:
not-existing); message exception details (1) are:
Failed message 1:
javax.mail.MessagingException: Connection error (java.net.UnknownHostException:
not-existing)
{code}
> TaskTestITCase failures
> ---
>
> Key: SYNCOPE-456
> URL: https://issues.apache.org/jira/browse/SYNCOPE-456
> Project: Syncope
> Issue Type: Bug
> Components: core
>Affects Versions: 1.2.0
>Reporter: Hadrian Zbarcea
>Assignee: Hadrian Zbarcea
>
> Both issueSYNCOPE81 and issueSYNCOPE86 fail on my system. The symptom is that
> TaskController.execute hangs (the line below is the last in the log) and then
> there is a timeout on the client side.
> 22:46:09.087 DEBUG org.apache.syncope.core.rest.controller.ControllerHandler
> - Before TaskController.execute([101, false])
> I am not sure if anybody saw this, if so please add a comment. I reproduce
> the issue consistently on my Ubuntu laptop with both sun and openjdk 6.
> Others don't see it in an environment similar to mine. I also saw it on a
> CentOS server. I cannot reproduce it on osx though. It is quite likely
> related to the environment, but nevertheless syncope should be more robust
> and handle errors gracefully in a misconfigured environment.
> Since I have environments that both work and don't, I will try to dig deeper,
> compare the two and see what the culprit is.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Created] (SYNCOPE-456) TaskTestITCase failures
Hadrian Zbarcea created SYNCOPE-456: --- Summary: TaskTestITCase failures Key: SYNCOPE-456 URL: https://issues.apache.org/jira/browse/SYNCOPE-456 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.2.0 Reporter: Hadrian Zbarcea Assignee: Hadrian Zbarcea Both issueSYNCOPE81 and issueSYNCOPE86 fail on my system. The symptom is that TaskController.execute hangs (the line below is the last in the log) and then there is a timeout on the client side. 22:46:09.087 DEBUG org.apache.syncope.core.rest.controller.ControllerHandler - Before TaskController.execute([101, false]) I am not sure if anybody saw this, if so please add a comment. I reproduce the issue consistently on my Ubuntu laptop with both sun and openjdk 6. Others don't see it in an environment similar to mine. I also saw it on a CentOS server. I cannot reproduce it on osx though. It is quite likely related to the environment, but nevertheless syncope should be more robust and handle errors gracefully in a misconfigured environment. Since I have environments that both work and don't, I will try to dig deeper, compare the two and see what the culprit is. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (SYNCOPE-449) Fix support for Eclipse IDE
[ https://issues.apache.org/jira/browse/SYNCOPE-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hadrian Zbarcea resolved SYNCOPE-449. - Resolution: Fixed Awesome, thanks! > Fix support for Eclipse IDE > --- > > Key: SYNCOPE-449 > URL: https://issues.apache.org/jira/browse/SYNCOPE-449 > Project: Syncope > Issue Type: Task > Components: build-tools >Affects Versions: 1.1.4 >Reporter: Hadrian Zbarcea >Assignee: Hadrian Zbarcea > Fix For: 1.1.5, 1.2.0 > > Attachments: syncope-449-1.patch > > > Trying to load syncope in eclipse gave me the same frustration [1] reported > by others. > Most of the issues are related to the use of the maven plugins not supported > by m2e. but I believe there are solutions/workarounds for all. > [1] > http://blog.tirasa.net/blogs/index.php/ilgrosso/the-definitive-guide-to-maven -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (SYNCOPE-449) Fix support for Eclipse IDE
[ https://issues.apache.org/jira/browse/SYNCOPE-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13831573#comment-13831573 ] Hadrian Zbarcea commented on SYNCOPE-449: - Sure, that'd be great, thx. You're right, it took me some to figure out the reason for the antrun magic. That's the reason I linked this issue to SYNCOPE-448. > Fix support for Eclipse IDE > --- > > Key: SYNCOPE-449 > URL: https://issues.apache.org/jira/browse/SYNCOPE-449 > Project: Syncope > Issue Type: Task > Components: build-tools >Affects Versions: 1.1.4 >Reporter: Hadrian Zbarcea >Assignee: Hadrian Zbarcea > Fix For: 1.2.0 > > Attachments: syncope-449-1.patch > > > Trying to load syncope in eclipse gave me the same frustration [1] reported > by others. > Most of the issues are related to the use of the maven plugins not supported > by m2e. but I believe there are solutions/workarounds for all. > [1] > http://blog.tirasa.net/blogs/index.php/ilgrosso/the-definitive-guide-to-maven -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (SYNCOPE-449) Fix support for Eclipse IDE
[ https://issues.apache.org/jira/browse/SYNCOPE-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13831558#comment-13831558 ] Hadrian Zbarcea commented on SYNCOPE-449: - Uhm, if I did something it doesn't necessarily mean it's correct or complete, just my best effort at the time :). Please feel free to apply it wherever you think it's applicable, you're the experts. There is another patch coming, I think it's best to keep it open at this time, no need to create another jira. However, the second problem is not really an eclipse problem, it's just that eclipse is more unhappy with it. It's the double definition of DefaultAttributableTransformer. I think that's not the best solution from a few points of view, but a fix is non trivial. What I am doing now is to rename the one in tests as DoubleValueAttributableTransformer (which is semantically closer to what it does) and then change the spring config and the poms to make the transformer pluggable. On a second thought that could be part of another jira, I personally don't mind either way. If anybody thinks the solution is not good, please let me know. > Fix support for Eclipse IDE > --- > > Key: SYNCOPE-449 > URL: https://issues.apache.org/jira/browse/SYNCOPE-449 > Project: Syncope > Issue Type: Task > Components: build-tools >Affects Versions: 1.1.4 >Reporter: Hadrian Zbarcea >Assignee: Hadrian Zbarcea > Fix For: 1.2.0 > > Attachments: syncope-449-1.patch > > > Trying to load syncope in eclipse gave me the same frustration [1] reported > by others. > Most of the issues are related to the use of the maven plugins not supported > by m2e. but I believe there are solutions/workarounds for all. > [1] > http://blog.tirasa.net/blogs/index.php/ilgrosso/the-definitive-guide-to-maven -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (SYNCOPE-449) Fix support for Eclipse IDE
[ https://issues.apache.org/jira/browse/SYNCOPE-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hadrian Zbarcea updated SYNCOPE-449: Attachment: syncope-449-1.patch More of a workaround than a fix, configuring the lifecycle-mapping m2e plugin allows one to load the project in eclipse without errors. There is still the issue of the double definition of DefaultAttributableTransformer for which I'll propose a solution soon. > Fix support for Eclipse IDE > --- > > Key: SYNCOPE-449 > URL: https://issues.apache.org/jira/browse/SYNCOPE-449 > Project: Syncope > Issue Type: Task > Components: build-tools >Affects Versions: 1.1.4 >Reporter: Hadrian Zbarcea >Assignee: Hadrian Zbarcea > Fix For: 1.2.0 > > Attachments: syncope-449-1.patch > > > Trying to load syncope in eclipse gave me the same frustration [1] reported > by others. > Most of the issues are related to the use of the maven plugins not supported > by m2e. but I believe there are solutions/workarounds for all. > [1] > http://blog.tirasa.net/blogs/index.php/ilgrosso/the-definitive-guide-to-maven -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (SYNCOPE-449) Fix support for Eclipse IDE
[ https://issues.apache.org/jira/browse/SYNCOPE-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hadrian Zbarcea updated SYNCOPE-449: Description: Trying to load syncope in eclipse gave me the same frustration [1] reported by others. Most of the issues are related to the use of the maven plugins not supported by m2e. but I believe there are solutions/workarounds for all. [1] http://blog.tirasa.net/blogs/index.php/ilgrosso/the-definitive-guide-to-maven was: Trying to load syncope in eclipse gave me the same frustrationn[1] reported by others. Most of the issues are related to the use of the maven plugins not supported by m2e. but I believe there are solutions/workarounds for all. [1] http://blog.tirasa.net/blogs/index.php/ilgrosso/the-definitive-guide-to-maven > Fix support for Eclipse IDE > --- > > Key: SYNCOPE-449 > URL: https://issues.apache.org/jira/browse/SYNCOPE-449 > Project: Syncope > Issue Type: Task > Components: build-tools >Affects Versions: 1.1.4 >Reporter: Hadrian Zbarcea >Assignee: Hadrian Zbarcea > Fix For: 1.2.0 > > > Trying to load syncope in eclipse gave me the same frustration [1] reported > by others. > Most of the issues are related to the use of the maven plugins not supported > by m2e. but I believe there are solutions/workarounds for all. > [1] > http://blog.tirasa.net/blogs/index.php/ilgrosso/the-definitive-guide-to-maven -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (SYNCOPE-449) Fix support for Eclipse IDE
[ https://issues.apache.org/jira/browse/SYNCOPE-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hadrian Zbarcea updated SYNCOPE-449: Description: Trying to load syncope in eclipse gave me the same frustrationn[1] reported by others. Most of the issues are related to the use of the maven plugins not supported by m2e. but I believe there are solutions/workarounds for all. [1] http://blog.tirasa.net/blogs/index.php/ilgrosso/the-definitive-guide-to-maven was: Trying to load syncope in eclipse gave me the same [frustration|http://blog.tirasa.net/blogs/index.php/ilgrosso/the-definitive-guide-to-maven] reported by others. Most of the issues are related to the use of the maven plugins not supported by m2e. but I believe there are solutions/workarounds for all. > Fix support for Eclipse IDE > --- > > Key: SYNCOPE-449 > URL: https://issues.apache.org/jira/browse/SYNCOPE-449 > Project: Syncope > Issue Type: Task > Components: build-tools >Affects Versions: 1.1.4 >Reporter: Hadrian Zbarcea > Fix For: 1.2.0 > > > Trying to load syncope in eclipse gave me the same frustrationn[1] reported > by others. > Most of the issues are related to the use of the maven plugins not supported > by m2e. but I believe there are solutions/workarounds for all. > [1] > http://blog.tirasa.net/blogs/index.php/ilgrosso/the-definitive-guide-to-maven -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Assigned] (SYNCOPE-449) Fix support for Eclipse IDE
[ https://issues.apache.org/jira/browse/SYNCOPE-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hadrian Zbarcea reassigned SYNCOPE-449: --- Assignee: Hadrian Zbarcea > Fix support for Eclipse IDE > --- > > Key: SYNCOPE-449 > URL: https://issues.apache.org/jira/browse/SYNCOPE-449 > Project: Syncope > Issue Type: Task > Components: build-tools >Affects Versions: 1.1.4 >Reporter: Hadrian Zbarcea >Assignee: Hadrian Zbarcea > Fix For: 1.2.0 > > > Trying to load syncope in eclipse gave me the same frustrationn[1] reported > by others. > Most of the issues are related to the use of the maven plugins not supported > by m2e. but I believe there are solutions/workarounds for all. > [1] > http://blog.tirasa.net/blogs/index.php/ilgrosso/the-definitive-guide-to-maven -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (SYNCOPE-449) Fix support for Eclipse IDE
Hadrian Zbarcea created SYNCOPE-449: --- Summary: Fix support for Eclipse IDE Key: SYNCOPE-449 URL: https://issues.apache.org/jira/browse/SYNCOPE-449 Project: Syncope Issue Type: Task Components: build-tools Affects Versions: 1.1.4 Reporter: Hadrian Zbarcea Fix For: 1.2.0 Trying to load syncope in eclipse gave me the same [frustration|http://blog.tirasa.net/blogs/index.php/ilgrosso/the-definitive-guide-to-maven] reported by others. Most of the issues are related to the use of the maven plugins not supported by m2e. but I believe there are solutions/workarounds for all. -- This message was sent by Atlassian JIRA (v6.1#6144)
